Triple
T32258756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eulerian digraph |
E824091
|
entity |
| Predicate | hasEdgeTraversal |
P178092
|
FINISHED |
| Object | Eulerian circuit starts and ends at the same vertex |
—
|
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: Eulerian circuit starts and ends at the same vertex | Statement: [Eulerian digraph, hasEdgeTraversal, Eulerian circuit starts and ends at the same vertex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEdgeTraversal Context triple: [Eulerian digraph, hasEdgeTraversal, Eulerian circuit starts and ends at the same vertex]
-
A.
hasEdge
Indicates that there exists a direct connection or link (an edge) between two entities in a graph or network.
-
B.
hasTrailConnection
Indicates that one location is connected to another by a traversable trail or path.
-
C.
hasEdgeGraph
Indicates that there is an edge (a direct connection or link) present within a graph between specified nodes or components.
-
D.
hasTrailDestination
Indicates that a trail leads to or ends at a particular destination.
-
E.
enablesTraversal
Indicates that one entity provides the means or capability for another entity to move through, across, or along something.
- F. None of above. chosen
Provenance (4 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: May 1, 2026, 12:41 a.m.