Triple
T19108792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eulerian trail |
E467732
|
entity |
| Predicate | mayStartAndEndAtDifferentVertices |
P134430
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eulerian trail, mayStartAndEndAtDifferentVertices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayStartAndEndAtDifferentVertices Context triple: [Eulerian trail, mayStartAndEndAtDifferentVertices, true]
-
A.
hasCabAtEachEnd
Indicates that something (typically a vehicle or train) has a cab located at both of its ends.
-
B.
hadCrossingPoints
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
C.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
D.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
E.
hasStartFinishOn
Indicates that an event, process, or activity begins and ends on a specified time, date, or boundary.
- 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.