Triple

T3486289
Position Surface form Disambiguated ID Type / Status
Subject M-153 (Ford Road) E73613 entity
Predicate terminusDirectionWest P34413 FINISHED
Object west terminus in Canton Township 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: west terminus in Canton Township area | Statement: [M-153 (Ford Road), terminusDirectionWest, west terminus in Canton Township area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terminusDirectionWest
Context triple: [M-153 (Ford Road), terminusDirectionWest, west terminus in Canton Township area]
  • A. terminusDirection chosen
    Indicates the directional orientation or endpoint direction associated with a route, path, or line.
  • B. terminusWestNear
    Indicates that the western terminus of one entity is located near the western terminus of another entity.
  • C. terminusEast
    Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
  • D. terminusWestConnection
    Indicates that one entity serves as the western endpoint where it connects to another entity or route.
  • E. terminusWestBorough
    Indicates that something serves as the western terminus or endpoint of a route, line, or connection at a place called Borough.
  • 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.