Grothendieck construction for functors to the category of relations One important case of the Grothedieck construction is the category of elements. We can get a similar construction when the underlying functor is of the type $F:\mathcal C\rightarrow Rel$, where $Rel$ is the category whose objects are sets and morphisms are binary relations.
Similarly to how Spivak, p.194, Definition 4.6.2.1 defined the category of elements, we can define this "category of relational elements" as the category $\Gamma(F)$ whose objects and morphisms are generated as follows: $$Ob(\Gamma(F)):=\{(C,c):C\in Ob(\mathcal C) \wedge c\in F(C)\}$$
$$Hom_{\Gamma(F)}((C,c),(C',c')):=\{f:C\rightarrow C':(c,c')\in F(f)\}$$
I cannot quite grasp how we can identify arrows in $\Gamma(F)$ as arrows in $\mathcal C$. For example, if $F$ is simply inclusion of categories, and $C=\{c\}$ and $C'=\{c'_1,c'_2\}$ and we have only one arrow $f=\{(c,c'_1),(c,c'_2)\}$, we still should get two arrows in $\Gamma(F)$, that is:
$$(C,c)\rightarrow(C',c'_1)$$
$$(C,c)\rightarrow(C',c'_2)$$
each one corresponding to an element of $f$. Instead, the definition of the homclasses suggests that there is only one arrow in $\Gamma(F)$, corresponding to $f$.
The question is: is this definition of the homclasses strictly correct, or should it be modified in some way?
 A: Sorry for my confusion in the comments.
You are completely right, it's the same problem as for slice categories for instance, or categories of arrows. 
Let me take the slice category example. Given an object $A$ of a category $C$ one may form $C/A$, the category whose objects are maps $X\to A$ and a morphism from $X\to A$ to $Y\to A$ is a map $X\to Y$ making the obvious diagram commute. 
But we are left with the same problem; i.e. with that definition we may very well have $Hom_{C/A}(c,d) \cap Hom_{C/A}(e,f) \neq \emptyset$ for different objects $c\neq e, d\neq f$; and that's problematic.
Some authors don't mind this; but (I think) most do.
To solve this problem you can either say "we know what we mean; it's clear from context", or from the formal point of view the (in my opinion) best approach is to add the domain and codomain in the data of the arrow : that is in your case an arrow $(C,c)\to (D,d)$ will be a triple $(f, (C,c), (D,d))$ where $f: C\to D$ is an arrow (or you could say it's a triple $(f,c,d)$ that doesn't really matter since the data of $C,D$ is already contained in $f$); and of course the same trick works for slice categories and arrow categories for instance.
