Triple
T12033061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A217 road |
E286459
|
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: [A217 road, hasJunctionWith, A232 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A232 road Context triple: [A217 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.
A233 road
The A233 road is a regional route in southeast England that connects the town of Westerham with nearby areas, including access toward Biggin Hill and the A21.
-
C.
A234 road
The A234 road is a minor A-road in southeast London that connects areas such as Penge with other parts of the city’s local road network.
-
D.
A223 road
The A223 road is a primary route in southeast London and northwest Kent, connecting areas such as Bexley, Sidcup, and Ruxley to the wider road network.
-
E.
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.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9040724ec8190808f334013ddc6d6 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a074701a1108190a284c91e003b7222 |
completed | May 15, 2026, 4:17 p.m. |
Created at: April 8, 2026, 9:47 p.m.