Triple
T18160055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscoda County, Michigan |
E434733
|
entity |
| Predicate | hasMajorHighway |
P385
|
FINISHED |
| Object | M-72 |
—
|
NE NERFINISHED |
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-72 | Statement: [Oscoda County, Michigan, hasMajorHighway, M-72]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-72 Context triple: [Oscoda County, Michigan, hasMajorHighway, M-72]
-
A.
M-72
chosen
M-72 is a state highway in northern Michigan that serves as a key east–west route connecting Traverse City with several inland communities and recreational areas.
-
B.
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.
-
C.
M-20
M-20 is a state trunkline highway in Michigan that runs east–west across the central part of the state, connecting communities such as Midland to the broader regional road network.
-
D.
M-77
M-77 is a state highway in Michigan, United States, running north–south through the eastern Upper Peninsula.
-
E.
M-24
M-24 is a state highway in Michigan that serves as a key north–south transportation route through communities such as Orion Township.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec0e0388190af11ac167411da96 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 10:30 a.m.