Triple
T4055321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M67 |
E84679
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M67 |
E84679
|
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: M67 | Statement: [M67, roadNumber, M67]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M67 Context triple: [M67, roadNumber, M67]
-
A.
M67
chosen
M67 is a short motorway in Greater Manchester, England, connecting the M60 near Denton towards Hyde and intended as the first section of an unrealized trans-Pennine route.
-
B.
M66
M66 is a motorway in Greater Manchester, England, forming part of the route between Manchester and the M62 near Bury.
-
C.
M57
M57 is a major motorway in Merseyside, England, forming part of the road network serving the Sefton area and connecting it to other key routes in the region.
-
D.
M42
M42 is a major motorway in the West Midlands region of England that forms part of the orbital route around Birmingham and connects several key motorways.
-
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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562a0f19c819084d23c3802ce8ca6 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.