Triple
T22005368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartshorne |
E543437
|
entity |
| Predicate | parishChurchStatus |
P82983
|
FINISHED |
| Object | historic parish church |
—
|
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 parish church | Statement: [Hartshorne, parishChurchStatus, historic parish church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishChurchStatus Context triple: [Hartshorne, parishChurchStatus, historic parish church]
-
A.
parishChurchHeritageStatus
chosen
Indicates the officially recognized heritage or protection status assigned to a parish church.
-
B.
isActiveParishChurch
Indicates that a church currently functions as the main parish church for a community and is actively in use for parish activities and services.
-
C.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
D.
formerChurchBuildingPreservationStatus
Indicates the preservation or protection status assigned to a building that formerly served as a church.
-
E.
hasParishStatusInChurchOfEngland
Indicates that an entity holds official parish status within the organizational structure of the Church of England.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276d81e4819083a40e51249e7fd7 |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:21 p.m.