Triple
T3486290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-153 (Ford Road) |
E73613
|
entity |
| Predicate | terminusDirectionEast |
P3569
|
FINISHED |
| Object | east terminus in Detroit–Dearborn area |
—
|
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: east terminus in Detroit–Dearborn area | Statement: [M-153 (Ford Road), terminusDirectionEast, east terminus in Detroit–Dearborn area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusDirectionEast Context triple: [M-153 (Ford Road), terminusDirectionEast, east terminus in Detroit–Dearborn area]
-
A.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
B.
terminusEast
chosen
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
D.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
terminusWestNear
Indicates that the western terminus of one entity is located near the western terminus of another entity.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9059f881908f9cbe544365c8df |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.