Triple
T2115036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Britain A roads |
E42590
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | A2 road |
E105226
|
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: A2 road | Statement: [Great Britain A roads, hasComponent, A2 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A2 road Context triple: [Great Britain A roads, hasComponent, A2 road]
-
A.
A2 road
chosen
The A2 road is a major route in southeast England connecting London to the port of Dover and forming part of a key corridor to mainland Europe.
-
B.
A20 road
The A20 road is a major route in southeast England that links London with the Channel port of Dover, serving as an important corridor for traffic to and from continental Europe.
-
C.
A4 road
The A4 road is a major historic route in England that runs west from central London through key cities such as Reading, Bath, and Bristol toward Avonmouth.
-
D.
A5 road
The A5 road is a major historic route in Great Britain running from London to Holyhead, forming part of the key connection between England and Wales.
-
E.
A22 road
The A22 road is a major route in southeast England connecting London with Eastbourne on 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0724e08190a0a4210d86261d6d |
completed | March 7, 2026, 5:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b6720949bc8190923e135c80185504 |
completed | March 15, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:43 p.m.