Triple
T22051426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wick parish |
E544892
|
entity |
| Predicate | hasReligiousJurisdictionType |
P16389
|
FINISHED |
| Object | 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: parish | Statement: [Wick parish, hasReligiousJurisdictionType, parish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousJurisdictionType Context triple: [Wick parish, hasReligiousJurisdictionType, parish]
-
A.
hasFormerReligiousJurisdiction
Indicates that an entity was previously under the religious authority or governance of another entity, but no longer is.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
religiousJurisdiction
chosen
Indicates that one entity holds official religious authority or governance over another entity or area.
-
D.
hasFictionalReligiousJurisdiction
Indicates that one entity holds an invented or fictional religious authority, control, or governance over another entity within a narrative or imaginary context.
-
E.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1283386f081908b70df81f38a5b1c |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:26 p.m.