Triple
T16210327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darnhall |
E393445
|
entity |
| Predicate | historicalParishType |
P13874
|
FINISHED |
| Object | ancient parish |
—
|
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: ancient parish | Statement: [Darnhall, historicalParishType, ancient parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalParishType Context triple: [Darnhall, historicalParishType, ancient parish]
-
A.
isHistoricParishOf
Indicates that one entity is a historic parish that formerly served, or is recognized as having served, as the parish jurisdiction for another entity.
-
B.
hasHistoricParishCharacter
Indicates that something possesses the distinctive qualities or attributes traditionally associated with a historic parish.
-
C.
hasParishHistory
Indicates that an entity possesses or is associated with a documented historical record of a parish.
-
D.
hasParishType
chosen
Indicates that an entity is associated with or classified by a specific type or category of parish.
-
E.
historicalTownshipOf
Indicates that one entity was formerly a township encompassing or governing the other entity during a past historical period.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22713282481909c7c0d0782213461 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.