Triple
T3652544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dronfield |
E77452
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | DRONFIELD |
E77452
|
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: DRONFIELD | Statement: [Dronfield, hasPostTown, DRONFIELD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DRONFIELD Context triple: [Dronfield, hasPostTown, DRONFIELD]
-
A.
Dronfield
chosen
Dronfield is a small town in Derbyshire, England, situated between Sheffield and Chesterfield and known for its historic buildings and residential character.
-
B.
Henfield
Henfield is a large historic village and civil parish in the Horsham District of West Sussex, England, known for its rural character and community amenities.
-
C.
Mirfield
Mirfield is a small town in West Yorkshire, England, known for its position on major rail routes and its historic textile industry.
-
D.
Tatsfield
Tatsfield is a village and civil parish in the Tandridge district of Surrey, England, situated near the border with Greater London and Kent.
-
E.
Duffield
Duffield is a village and civil parish in Derbyshire, England, situated north of Derby on the River Derwent.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b805a48190a7bc230a382365d6 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b44f435c088190976c1dab165665f1 |
completed | March 13, 2026, 5:54 p.m. |
Created at: March 8, 2026, 3:24 p.m.