Triple
T16056852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochford, Essex, England |
E389501
|
entity |
| Predicate | nearSettlement |
P3883
|
FINISHED |
| Object | Ashingdon |
E441016
|
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: Ashingdon | Statement: [Rochford, Essex, England, nearSettlement, Ashingdon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ashingdon Context triple: [Rochford, Essex, England, nearSettlement, Ashingdon]
-
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.
Canewdon
Canewdon is a historic rural village in Essex, England, noted for its ancient church, associations with witchcraft folklore, and views over the River Crouch.
-
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.
Ockendon
Ockendon is a settlement in the borough of Thurrock in Essex, England, known for its suburban character and proximity to London.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1837579488190964ca004c2eb01c4 |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbe49bd0819088e25de082184133 |
completed | May 10, 2026, 1:14 a.m. |
Created at: April 10, 2026, 4:56 a.m.