Triple
T3353380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A59 road |
E70547
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | A59 |
E223757
|
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: A59 | Statement: [A59 road, roadNumber, A59]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A59 Context triple: [A59 road, roadNumber, A59]
-
A.
A59
chosen
A59 is a major road in northern England that runs between Liverpool and York, passing through key towns such as Preston and Skipton.
-
B.
A56
The A56 is a major road in North West England that runs between Chester and Broughton, passing through key urban areas including Manchester.
-
C.
A529
A529 is a regional road in England that connects the town of Market Drayton to other nearby areas within the local road network.
-
D.
A9
A9 is a major German autobahn that runs north–south, connecting Berlin with Munich and passing through regions such as Middle Franconia.
-
E.
A359
A359 is the ICAO aircraft type designator for the Airbus A350-900, a long-range, wide-body twin-engine jet airliner used primarily for international passenger flights.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb23ec53881908a04c7f784fe8c43 |
completed | March 8, 2026, 5:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b32532ebd08190bf174d72fba89a75 |
completed | March 12, 2026, 8:42 p.m. |
Created at: March 8, 2026, 3:13 p.m.