Triple
T10901148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wexford County |
E257443
|
entity |
| Predicate | hasMajorHighway |
P385
|
FINISHED |
| Object | M-55 |
E888748
|
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-55 | Statement: [Wexford County, hasMajorHighway, M-55]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-55 Context triple: [Wexford County, hasMajorHighway, M-55]
-
A.
M-55
chosen
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.
-
B.
M-5
M-5 is a state highway in southeastern Michigan that serves as a key commuter route connecting Novi and surrounding suburbs to the Detroit metropolitan area.
-
C.
M-50
M-50 is a major orbital motorway around Madrid, Spain, designed to divert traffic from the city center and connect key suburbs and highways.
-
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-59
M-59 is an east–west state highway in southeastern Michigan that serves as a major suburban arterial route connecting communities north of Detroit.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a3e83c81908dc48c0fb7935da7 |
completed | April 9, 2026, 8:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e155306e9081909433522eeecf2b7d |
completed | April 16, 2026, 9:31 p.m. |
Created at: April 8, 2026, 9:22 p.m.