Triple
T7890551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M56 |
E183219
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M56 |
E183219
|
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: M56 | Statement: [M56, roadNumber, M56]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M56 Context triple: [M56, roadNumber, M56]
-
A.
M56
chosen
The M56 is a major motorway in North West England that connects Manchester to North Wales and serves as a key route to Manchester Airport.
-
B.
M55
M55 is a New York City bus route that provides public transit service connecting to the Whitehall Terminal area in Lower Manhattan.
-
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.
M53
M53 is a major motorway in North West England that connects the Wirral Peninsula with the M56 near Chester, facilitating regional traffic flow.
-
E.
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.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39ee137081908e87e35016c3a176 |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b9f47cc8190a6f9fc087010ad96 |
completed | March 31, 2026, 5:29 a.m. |
Created at: March 30, 2026, 5 p.m.