Triple
T20456000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belper |
E501786
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Duffield |
—
|
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: Duffield | Statement: [Belper, hasNearbySettlement, Duffield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Duffield Context triple: [Belper, hasNearbySettlement, Duffield]
-
A.
Duffield
chosen
Duffield is a village and civil parish in Derbyshire, England, situated north of Derby on the River Derwent.
-
B.
Darfield
Darfield is a small rural service town in the Canterbury region of New Zealand’s South Island, known as a gateway to nearby ski fields and outdoor recreation areas.
-
C.
Darfield
Darfield is a village in South Yorkshire, England, historically associated with coal mining and situated near the River Dearne.
-
D.
Douglasfield
Douglasfield is a locality in Scotland situated near the Dighty Water stream.
-
E.
Crossford
Crossford is a small village situated in Scotland’s Clyde Valley, known for its rural character and surrounding agricultural landscape.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a0dd188190ab6cbb387d9c0c1d |
completed | April 20, 2026, 9:12 p.m. |
Created at: April 16, 2026, 11:32 a.m.