Triple
T6375719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Borough of Hackney |
E143459
|
entity |
| Predicate | hasMajorRoad |
P385
|
FINISHED |
| Object | A12 |
E220828
|
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: A12 | Statement: [London Borough of Hackney, hasMajorRoad, A12]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A12 Context triple: [London Borough of Hackney, hasMajorRoad, A12]
-
A.
A12
chosen
The A12 is a major road in England that connects London with East Anglia, serving key towns and cities including Ipswich and Colchester.
-
B.
A12
A12 is a major Swiss motorway that connects the regions of Bern and Fribourg, serving as an important north–south transit corridor.
-
C.
A13
A13 is a major Swiss motorway running along the country’s eastern side, providing an important north–south transit route through the Alps.
-
D.
A13
A13 is a major road in England that serves as a key route linking London with areas in south Essex, including Basildon.
-
E.
A14
A14 is a major trunk road in England that forms a key east–west freight and commuter route linking the Midlands to the East Coast ports.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683bfc7081908b15c3c9a3c72e7b |
completed | March 22, 2026, 10:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638724d448190a7f13a7c449341db |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:33 p.m.