Triple
T13616022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clopton |
E325308
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Clopton |
E325308
|
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: Clopton | Statement: [Clopton, civilParish, Clopton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clopton Context triple: [Clopton, civilParish, Clopton]
-
A.
Clopton
chosen
Clopton is a small rural village and civil parish located in the English county of Suffolk.
-
B.
Digbeth
Digbeth is a historic inner-city district of Birmingham, England, known for its industrial heritage and vibrant creative and nightlife scenes.
-
C.
Holmesdale
Holmesdale is a residential suburb of the town of Dronfield in Derbyshire, England.
-
D.
Stechford
Stechford is a suburban area of Birmingham, England, historically part of Warwickshire and known for its residential character and railway connections.
-
E.
Kings Norton
Kings Norton is a suburban area in the south of Birmingham, England, known for its historic village green, conservation area, and mix of residential and green spaces.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0ad0a7c81909c7972187202db96 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78ae7d6908190836172e955b0d7e8 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:50 p.m.