Triple
T4248279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeadon Loop |
E95580
|
entity |
| Predicate | municipality |
P852
|
FINISHED |
| Object | Yeadon |
E95580
|
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: Yeadon | Statement: [Yeadon Loop, municipality, Yeadon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yeadon Context triple: [Yeadon Loop, municipality, Yeadon]
-
A.
Yeadon
Yeadon is a town in West Yorkshire, England, situated northwest of Leeds and known for its proximity to Leeds Bradford Airport.
-
B.
Lydbrook
Lydbrook is a village in Gloucestershire, England, situated in the Wye Valley on the edge of the Forest of Dean and historically known for its coal mining and industrial heritage.
-
C.
Sowerby Bridge
Sowerby Bridge is a market town in Calderdale, West Yorkshire, England, known for its industrial heritage, canal and railway junctions, and position in the Upper Calder Valley.
-
D.
Yeadon Loop
chosen
Yeadon Loop is a trolley turning loop and terminal facility in Yeadon, Pennsylvania, serving as the western endpoint of SEPTA’s Route 13.
-
E.
Longwell Green
Longwell Green is a suburban area and civil parish in South Gloucestershire, England, situated on the eastern outskirts of Bristol.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9cb71481909b4baa370193148f |
completed | March 12, 2026, 11:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5a87c033881908e0cf9fdfecaf36a |
completed | March 14, 2026, 6:27 p.m. |
Created at: March 12, 2026, 11:06 p.m.