Triple
T19108790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eulerian trail |
E467732
|
entity |
| Predicate | traversesEveryEdge |
P134428
|
FINISHED |
| Object | exactly once |
—
|
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: exactly once | Statement: [Eulerian trail, traversesEveryEdge, exactly once]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversesEveryEdge Context triple: [Eulerian trail, traversesEveryEdge, exactly once]
-
A.
alsoTraverses
Indicates that a route, path, or entity passes through or crosses an additional location or segment beyond its primary traversal.
-
B.
formerTraversal
Indicates that one entity previously traversed, passed through, or traveled along another entity, but is no longer doing so.
-
C.
traversesIsland
Indicates that an entity moves across or through an island, passing over its land area.
-
D.
hasEdgeCount
Indicates that there is a specified number of edges associated with an entity, such as a graph or geometric shape.
-
E.
hasEdge
Indicates that there exists a direct connection or link (an edge) between two entities in a graph or network.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e391f00c8190881a5977dd3728ed |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.