Triple
T11970824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergland, Michigan |
E284913
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | M-64 |
E292085
|
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-64 | Statement: [Bergland, Michigan, locatedOn, M-64]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-64 Context triple: [Bergland, Michigan, locatedOn, M-64]
-
A.
M-64
chosen
M-64 is a state trunkline highway in Michigan’s Upper Peninsula that runs through Gogebic County and serves as a key north–south route near the Lake Superior shoreline.
-
B.
M-66
M-66 is a state trunkline highway in Michigan that runs north–south through the northern Lower Peninsula, including Emmet County.
-
C.
M-69
M-69 is a state trunkline highway in Michigan’s Upper Peninsula that runs east–west through rural areas including Delta County.
-
D.
M-46
M-46 is an east–west state trunkline highway in Michigan that spans much of the state's Lower Peninsula, connecting several communities across multiple counties.
-
E.
M-68
M-68 is a state trunkline highway in northern Michigan that serves as an east–west route across parts of the northern Lower Peninsula.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f459691ff0819099282172933d2d81 |
completed | May 1, 2026, 7:42 a.m. |
Created at: April 8, 2026, 9:46 p.m.