Triple
T28464195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draycot Cerne |
E720243
|
entity |
| Predicate | formerParishStatus |
P81469
|
FINISHED |
| Object | abolished |
—
|
LITERAL 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: abolished | Statement: [Draycot Cerne, formerParishStatus, abolished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerParishStatus Context triple: [Draycot Cerne, formerParishStatus, abolished]
-
A.
ecclesiasticalParishStatus
Indicates the formal ecclesiastical status or standing of a parish within a church’s organizational structure.
-
B.
formerCivilParish
chosen
Indicates that an entity was once designated as a civil parish but no longer holds that administrative status.
-
C.
parishStatusBeforeCathedral
Indicates the status or condition of a parish as it existed prior to the establishment or designation of a cathedral.
-
D.
hasAncientParishStatus
Indicates that an entity possesses the legal or historical status of being an ancient parish.
-
E.
formerParishChurchRelocatedTo
Indicates that a building which once served as a parish church has been moved from its original location to a new site.
- F. None of above.
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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 28, 2026, 2:43 a.m.