Triple
T36871345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayley graph |
E911229
|
entity |
| Predicate | hasEdgeDefinition |
P2185
|
FINISHED |
| Object | edges connect elements differing by a generator |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: edges connect elements differing by a generator | Statement: [Cayley graph, hasEdgeDefinition, edges connect elements differing by a generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEdgeDefinition Context triple: [Cayley graph, hasEdgeDefinition, edges connect elements differing by a generator]
-
A.
hasEdge
Indicates that there exists a direct connection or link (an edge) between two entities in a graph or network.
-
B.
hasEdgeGraph
Indicates that there is an edge (a direct connection or link) present within a graph between specified nodes or components.
-
C.
hasDefinition
chosen
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
D.
hasEdgeCount
Indicates that there is a specified number of edges associated with an entity, such as a graph or geometric shape.
-
E.
hasEdgeVersionStatement
Indicates that there exists a specific version-related statement associated with an edge in a graph or network.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.