Triple
T3750352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A243 road |
E81313
|
entity |
| Predicate | junctionWith |
P1018
|
FINISHED |
| Object | A24 road |
E18813
|
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: A24 road | Statement: [A243 road, junctionWith, A24 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A24 road Context triple: [A243 road, junctionWith, A24 road]
-
A.
A24 road
chosen
The A24 road is a major route in southeast England that connects London to the south coast, passing through counties such as Surrey and West Sussex.
-
B.
A22 road
The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
-
C.
A14 road
The A14 road is a major trunk route in England that links the Midlands to the East Coast, serving as a key freight and commuter corridor including through Cambridgeshire.
-
D.
A21 road
The A21 road is a major route in southeast England that connects London with Hastings on the south coast, passing through Kent and East Sussex.
-
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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6d0ac4819092c9a41cc60f518d |
completed | March 8, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94aceb7108190beeec78587c04161 |
completed | April 10, 2026, 7:09 p.m. |
Created at: March 8, 2026, 3:35 p.m.