Triple
T17433481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scagglethorpe |
E423935
|
entity |
| Predicate | roadAccess |
P385
|
FINISHED |
| Object | A64 |
—
|
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: A64 | Statement: [Scagglethorpe, roadAccess, A64]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A64 Context triple: [Scagglethorpe, roadAccess, A64]
-
A.
A64
chosen
The A64 is a major road in northern England that links Leeds and York with the coastal town of Scarborough.
-
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.
A60
A60 is a major road in England that runs through Nottinghamshire and connects Nottingham with surrounding towns including West Bridgford and Loughborough.
-
D.
A635
A635 is a major road in Greater Manchester, England, forming part of the regional route network connecting Manchester with surrounding towns.
-
E.
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.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4490274608190a60ada9aeb246eff |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.