Triple
T8037198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary Redcliffe, Bristol |
E187136
|
entity |
| Predicate | denominationRite |
P978
|
FINISHED |
| Object | Anglican |
—
|
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: Anglican | Statement: [St Mary Redcliffe, Bristol, denominationRite, Anglican]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationRite Context triple: [St Mary Redcliffe, Bristol, denominationRite, Anglican]
-
A.
hasDenominationRite
Indicates that an entity is associated with, practices, or follows a particular religious denomination or rite.
-
B.
denomination
chosen
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
-
C.
denominationType
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
D.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
E.
honoredInDenomination
Indicates that an individual or entity is formally recognized, venerated, or given special honor within a particular religious denomination.
- 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_69ca82ae2d1081909dbfee42b41db419 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f188e1c8190b92760c91d31f2df |
completed | March 31, 2026, 3:27 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:22 p.m.