Triple
T17690645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashingdon |
E441016
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Ashingdon village |
—
|
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: Ashingdon village | Statement: [Ashingdon, hasSettlement, Ashingdon village]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashingdon village Context triple: [Ashingdon, hasSettlement, Ashingdon village]
-
A.
Ashingdon
chosen
Ashingdon is a village and civil parish in Essex, England, known for its historic church and connections to the Battle of Assandun in 1016.
-
B.
Bletchingdon
Bletchingdon is a rural village in Oxfordshire, England, known for its historic parish church and traditional English countryside setting.
-
C.
Ashington
Ashington is a former coal-mining town in Northumberland, England, known for its industrial heritage and role in the region’s mining history.
-
D.
Ashington
Ashington is a village and civil parish in West Sussex, England, situated within the Horsham District.
-
E.
Biddeston
Biddeston is a small rural locality in the Toowoomba Region of Queensland, Australia, known for its agricultural landscape and close-knit community.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704b43a88190ba29654ca695839e |
completed | April 19, 2026, 6:03 a.m. |
Created at: April 10, 2026, 10:03 a.m.