Triple
T16945838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boroughbridge |
E411065
|
entity |
| Predicate | roadJunction |
P6234
|
FINISHED |
| Object | A1(M) and A168 |
E160628
|
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: A1(M) and A168 | Statement: [Boroughbridge, roadJunction, A1(M) and A168]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A1(M) and A168 Context triple: [Boroughbridge, roadJunction, A1(M) and A168]
-
A.
A1(M)
chosen
A1(M) is a series of motorway-standard sections in England that upgrade parts of the historic A1 route between London and the North.
-
B.
A-1M
The A-1M is an upgraded version of the Brazilian AMX A-1 attack aircraft featuring modernized avionics, sensors, and systems to enhance its ground-attack and reconnaissance capabilities.
-
C.
A-1
A-1 is the station code assigned to Kabaty, the southern terminus of Warsaw Metro Line M1.
-
D.
A-18
A-18 is the station code assigned to Asakusa Station on Tokyo’s Toei Asakusa Line.
-
E.
A1A
A1A is a scenic coastal highway in Florida that runs along the Atlantic Ocean, known for connecting popular beaches and tourist destinations.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb25e0c8190948e62d9575ae9cd |
completed | April 18, 2026, 6:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfeca4208190a3b9270869063d3d |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:31 a.m.