Triple
T18779283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheatley |
E459212
|
entity |
| Predicate | hasNearbyMotorwayJunction |
P16027
|
FINISHED |
| Object | M40 Junction 8A |
—
|
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: M40 Junction 8A | Statement: [Wheatley, hasNearbyMotorwayJunction, M40 Junction 8A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M40 Junction 8A Context triple: [Wheatley, hasNearbyMotorwayJunction, M40 Junction 8A]
-
A.
M40 Junction 8
chosen
M40 Junction 8 is a motorway junction on England’s M40 that provides access to the village of Wheatley and the surrounding Oxfordshire area.
-
B.
M1 Junction 8
M1 Junction 8 is a motorway junction on England’s M1 serving the Hemel Hempstead area, including the nearby village of Leverstock Green.
-
C.
M4 Junction 17
M4 Junction 17 is a motorway junction on England’s M4 serving the town of Chippenham and providing access to north Wiltshire.
-
D.
M4 Junction 16
M4 Junction 16 is a major motorway interchange on the M4 serving the town of Swindon in Wiltshire, England.
-
E.
M4 Junction 13
M4 Junction 13 is a motorway interchange on the M4 near Chieveley in Berkshire, England, providing access to Newbury and connecting with the A34.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933d2d048190a42480edc70bf086 |
completed | April 20, 2026, 2:45 a.m. |
Created at: April 10, 2026, 11:52 a.m.