Triple
T22259100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M27 |
E550170
|
entity |
| Predicate | hasJunction |
P1018
|
FINISHED |
| Object | Junction 8 |
—
|
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 8 | Statement: [M27, hasJunction, Junction 8]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Junction 8 Context triple: [M27, hasJunction, Junction 8]
-
A.
Junction 8
chosen
Junction 8 is a major interchange on England’s M20 motorway providing access to the town of Maidstone and connections toward the A20 and A249 routes.
-
B.
Junction 16
Junction 16 is a numbered motorway interchange on the M20 in England, connecting local roads to this major route between London and the Channel ports.
-
C.
Junction 22
Junction 22 is a high-altitude motorway junction on the M62 in northern England, situated on the Pennines near the motorway’s summit.
-
D.
Junction 7
Junction 7 is a numbered junction on England’s M58 motorway, serving as one of the route’s access and exit points.
-
E.
Junction 7
Junction 7 is an interchange on the M2 motorway in Northern Ireland, providing access to the nearby town of Antrim and surrounding areas.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c5b54c8190854690ba599639fa |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 16, 2026, 8:39 p.m.