Triple
T22592956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countesthorpe |
E564996
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Countesthorpe |
—
|
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: Countesthorpe | Statement: [Countesthorpe, civilParish, Countesthorpe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Countesthorpe Context triple: [Countesthorpe, civilParish, Countesthorpe]
-
A.
Countesthorpe
chosen
Countesthorpe is a large village and civil parish in the Blaby district of Leicestershire, England, situated just south of the city of Leicester.
-
B.
Apethorpe
Apethorpe is a village in Northamptonshire, England, known for its historic country house and rural character.
-
C.
Trusthorpe
Trusthorpe is a small coastal village in Lincolnshire, England, known for its quiet seaside character and proximity to the resort town of Sutton-on-Sea.
-
D.
Bilsthorpe
Bilsthorpe is a village and former mining community in Nottinghamshire, England.
-
E.
Lubbesthorpe
Lubbesthorpe is a small village and civil parish in Leicestershire, England, situated near Leicester and now associated with significant recent housing development.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f16163cb248190b377b110d80a6730 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 2:49 p.m.