Triple
T18473384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A635 road |
E451360
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | A635 |
—
|
NE NERFINISHED |
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: A635 | Statement: [A635 road, roadNumber, A635]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A635 Context triple: [A635 road, roadNumber, A635]
-
A.
A635
chosen
A635 is a major road in Greater Manchester, England, forming part of the regional route network connecting Manchester with surrounding towns.
-
B.
A63
A63 is a major French autoroute in southwestern France that connects Bordeaux to the Spanish border, forming part of a key European north–south transport corridor.
-
C.
A66
A66 is a major trans-Pennine road in northern England that connects the Lake District with the North East, serving as an important east–west transport route.
-
D.
A605
A605 is a primary road in eastern England that connects Peterborough with key nearby towns and routes, serving as an important regional transport link.
-
E.
A565
The A565 is a primary road in northwest England that connects Liverpool with Southport and passes through the Metropolitan Borough of Sefton.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e530617e48819091240d4405e53aaa |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:34 a.m.