Triple
T15336360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-59 freeway |
E366675
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | M-53 |
E300464
|
NE 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: M-53 | Statement: [M-59 freeway, hasJunctionWith, M-53]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-53 Context triple: [M-59 freeway, hasJunctionWith, M-53]
-
A.
M-53
chosen
M-53 is a state highway in Michigan that runs north–south through the Detroit metropolitan area and into Michigan’s Thumb region.
-
B.
M53
M53 is a major motorway in North West England that connects the Wirral Peninsula with the M56 near Chester, facilitating regional traffic flow.
-
C.
M-58
M-58 is a designated route or highway whose numbering directly precedes that of M-59 (Hall Road) in the same road system.
-
D.
M-52
M-52 is a state highway in Michigan that runs north–south through several counties, serving as an important regional route for local and through traffic.
-
E.
M-57
M-57 is an east–west state trunkline highway in Michigan that serves as a regional connector across several counties, including Montcalm County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e03c5f081908e4d14dbdbc7f7a6 |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01f11b88819089342e8b088bc95e |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.