Triple
T20058351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2 motorway |
E499399
|
entity |
| Predicate | hasJunction |
P1018
|
FINISHED |
| Object | Junction 2 |
—
|
NE NERFINISHED |
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: Junction 2 | Statement: [M2 motorway, hasJunction, Junction 2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Junction 2 Context triple: [M2 motorway, hasJunction, Junction 2]
-
A.
Junction 2
Junction 2 is a numbered interchange on the M66 motorway in Greater Manchester, England, providing access between the motorway and local road networks.
-
B.
Junction 2
chosen
Junction 2 is a numbered interchange on the M60 motorway in Greater Manchester, England, connecting local roads to the orbital route around Manchester.
-
C.
Junction 1
Junction 1 is a key interchange on the M60 motorway near Stockport, connecting local roads to the orbital route around Greater Manchester.
-
D.
Junction 1
Junction 1 is a motorway interchange on the M20 in southeast England, providing access between the M20 and local roads near the London orbital route.
-
E.
Junction 1
Junction 1 is a major road interchange on England’s M58 motorway, connecting it with local and regional routes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66373e0e08190a6d8a10084eecc4d |
completed | April 20, 2026, 5:33 p.m. |
Created at: April 11, 2026, 3:38 p.m.