Triple
T13581973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan State Highway 35 |
E324440
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | M-35 |
E900617
|
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-35 | Statement: [Michigan State Highway 35, abbreviation, M-35]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-35 Context triple: [Michigan State Highway 35, abbreviation, M-35]
-
A.
M-35
chosen
M-35 is a state trunkline highway in Michigan’s Upper Peninsula that runs along the shore of Green Bay and connects several communities in Menominee County and beyond.
-
B.
M-39
M-39 is a state highway in Michigan commonly known as the Southfield Freeway, serving as a major north–south commuter route in the Detroit metropolitan area.
-
C.
M-45
M-45 is a major ring road in the Madrid metropolitan area that helps divert traffic around the city and connect several eastern suburbs.
-
D.
M-45
M-45 is a state highway in Michigan that runs east–west through the Grand Rapids area toward the Lake Michigan shoreline.
-
E.
M-55
M-55 is a state trunkline highway in Michigan that runs east–west across the northern Lower Peninsula, connecting several communities including the city of Manistee.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb031e8048190a5f2ea934308036c |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bbf946c8190ba3d2b87cb11dc9d |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.