Triple
T871085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A24 road |
E18813
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | A232 road |
E146441
|
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: A232 road | Statement: [A24 road, hasJunctionWith, A232 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A232 road Context triple: [A24 road, hasJunctionWith, A232 road]
-
A.
A232 road
chosen
The A232 road is a major east–west route in South London and northwest Kent, connecting several suburbs and towns between Orpington and Ewell.
-
B.
A23 road
The A23 road is a major route in southern England connecting London to Brighton, serving as a key corridor between the capital and the south coast.
-
C.
A22 road
The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
-
D.
A243 road
The A243 road is a key route in Surrey, England, connecting the town of Leatherhead with nearby areas and linking to major roads such as the M25 and A24.
-
E.
A205 road
The A205 road is a major orbital route in London forming part of the South Circular Road, connecting various districts across the south of the city.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac94d5ac81909feee876696da589 |
completed | March 1, 2026, 9:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae1f9fcac481909cb3f6c6dc681e60 |
completed | March 9, 2026, 1:17 a.m. |
Created at: March 1, 2026, 7:39 p.m.