Triple
T16734009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A10 road |
E406669
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | A414 |
E365927
|
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: A414 | Statement: [A10 road, hasJunctionWith, A414]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A414 Context triple: [A10 road, hasJunctionWith, A414]
-
A.
A414
chosen
The A414 is a major east–west road in southern England that links several Hertfordshire towns and provides an important route near Welwyn Garden City.
-
B.
A41
The A41 is a major road in England that runs between London and Birkenhead, serving as an important route through the Midlands and Home Counties.
-
C.
A417
A417 is a major road in England that links key towns and routes in Gloucestershire and the surrounding region.
-
D.
A4174
The A4174 is a major ring road in the Bristol area of South Gloucestershire, England, providing key orbital and commuter routes around the city and its suburbs.
-
E.
A418
The A418 is a primary road in England that connects the town of Thame with other nearby settlements and major routes in the region.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c38c9cc8190a3220cc3684388dc |
completed | April 18, 2026, 2:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d4c723c8190ad92628f4164d11c |
completed | May 10, 2026, 2:59 p.m. |
Created at: April 10, 2026, 5:20 a.m.