Triple
T33563283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shurdington |
E859684
|
entity |
| Predicate | hasAnglicanParishChurch |
P191378
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shurdington, hasAnglicanParishChurch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnglicanParishChurch Context triple: [Shurdington, hasAnglicanParishChurch, true]
-
A.
isAnglicanParishChurchIn
Indicates that a church is an Anglican parish church located within a specified place or area.
-
B.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
C.
isParishChurchIn
Indicates that a church serves as the designated parish church for a specific parish or locality.
-
D.
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.
-
E.
hasParishStatusInChurchOfEngland
Indicates that an entity holds official parish status within the organizational structure of the Church of England.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 1, 2026, 1:40 a.m.