Triple
T21682233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian churches |
E535134
|
entity |
| Predicate | mayBeParishChurch |
P145430
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Christian churches, mayBeParishChurch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeParishChurch Context triple: [Christian churches, mayBeParishChurch, yes]
-
A.
isParishChurch
Indicates that a church holds the official status of the main church serving a particular parish within an ecclesiastical jurisdiction.
-
B.
isParishChurchIn
Indicates that a church serves as the designated parish church for a specific parish or locality.
-
C.
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.
-
D.
isAnglicanParishChurchIn
Indicates that a church is an Anglican parish church located within a specified place or area.
-
E.
hasParishChurchArchitecturalInterest
Indicates that a parish church possesses notable architectural features or significance.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c7c6a08190bbd9a89b8a3b921b |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:43 p.m.