Triple
T31734242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parish of Kinglassie |
E809947
|
entity |
| Predicate | ecclesiasticalParishStatus |
P172479
|
FINISHED |
| Object | historic |
—
|
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: historic | Statement: [parish of Kinglassie, ecclesiasticalParishStatus, historic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ecclesiasticalParishStatus Context triple: [parish of Kinglassie, ecclesiasticalParishStatus, historic]
-
A.
hasParishStatusInChurchOfEngland
Indicates that an entity holds official parish status within the organizational structure of the Church of England.
-
B.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
C.
parishChurchHeritageStatus
Indicates the officially recognized heritage or protection status assigned to a parish church.
-
D.
isParishEquivalent
Indicates that one administrative or ecclesiastical unit is considered equivalent in status or function to a parish.
-
E.
hasParishStatusSince
Indicates that an entity has held the status of a parish continuously starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:22 p.m.