Triple
T2986371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A21 road |
E80634
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | A26 road |
E511118
|
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: A26 road | Statement: [A21 road, connectsTo, A26 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A26 road Context triple: [A21 road, connectsTo, A26 road]
-
A.
A26 road
chosen
The A26 road is a major route in Northern Ireland that connects Ballymena with other key towns and regions, serving as an important corridor for local and regional traffic.
-
B.
A16 road
The A16 road is a major route in eastern England that runs through Lincolnshire and connects key towns such as Grimsby, Louth, and Spalding.
-
C.
A22 road
The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
-
D.
A6 road
The A6 road is a major long-distance route in England that runs from Luton in the south to Carlisle in the north, passing through several key towns and cities in the Midlands and North West.
-
E.
A28 road
The A28 road is a major route in southeast England that runs through Kent and East Sussex, linking towns such as Ashford and Canterbury.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c76dfc8190b08bd6110ffabf25 |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ca0812dcec819080c8386061d913b3 |
completed | March 30, 2026, 5:20 a.m. |
Created at: March 8, 2026, 2:59 p.m.