Triple
T3790613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junction 21 of M60 motorway |
E89635
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M60 |
E76610
|
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: M60 | Statement: [Junction 21 of M60 motorway, roadNumber, M60]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M60 Context triple: [Junction 21 of M60 motorway, roadNumber, M60]
-
A.
M60
chosen
M60 is a major orbital motorway encircling the city of Manchester in Greater Manchester, England.
-
B.
M61
M61 is a major motorway in North West England connecting Manchester with Preston and linking into the wider UK motorway network.
-
C.
M60 SBS
The M60 SBS is a Select Bus Service route in New York City that provides limited-stop service between Manhattan and Queens, including direct access to LaGuardia Airport.
-
D.
M62
M62 is a major trans-Pennine motorway in northern England connecting cities such as Liverpool, Manchester, Leeds, and Hull.
-
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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee76733248190a24a1143c64bd6c6 |
completed | March 9, 2026, 3:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4f055e3988190a1b3633e390c0d6f |
completed | March 14, 2026, 5:21 a.m. |
Created at: March 9, 2026, 3:15 p.m.