Triple
T10896459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northumberland Line |
E257321
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Ashington |
E256338
|
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: Ashington | Statement: [Northumberland Line, connects, Ashington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashington Context triple: [Northumberland Line, connects, Ashington]
-
A.
Ashington
chosen
Ashington is a former coal-mining town in Northumberland, England, known for its industrial heritage and role in the region’s mining history.
-
B.
Ashington
Ashington is a village and civil parish in West Sussex, England, situated within the Horsham District.
-
C.
Assington
Assington is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
D.
Ashburnham
Ashburnham is a small New England town in northern Massachusetts known for its rural character, lakes, and historic village center.
-
E.
Ashingdon
Ashingdon is a village and civil parish in Essex, England, known for its historic church and connections to the Battle of Assandun in 1016.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d022f4c81909cd9ea27a9f0cd32 |
completed | April 9, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4417f4dfc8190bd50cec0bc52a9cc |
completed | April 19, 2026, 2:44 a.m. |
Created at: April 8, 2026, 9:21 p.m.