Triple
T14642628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M5 motorway near Avonmouth |
E343764
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M5 |
E233858
|
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: M5 | Statement: [M5 motorway near Avonmouth, roadNumber, M5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M5 Context triple: [M5 motorway near Avonmouth, roadNumber, M5]
-
A.
M5
chosen
M5 is a major British motorway that runs through the West Midlands and South West England, connecting the Midlands to the South West peninsula.
-
B.
M5
M5 is a line of the Bucharest Metro rapid transit system serving parts of Romania’s capital city.
-
C.
M5
M5 is a New York City bus route that runs along Manhattan’s west side, connecting Lower Manhattan with uptown neighborhoods including Morningside Heights.
-
D.
M55
M55 is a New York City bus route that provides public transit service connecting to the Whitehall Terminal area in Lower Manhattan.
-
E.
M55
M55 is a British motorway in Lancashire that links the city of Preston with the seaside resort of Blackpool.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4e80aa48190884bab800f357106 |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5d404e881908d26e684702ae122 |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:26 a.m.