Triple
T1215113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Coventry |
E26090
|
entity |
| Predicate | hasDenominationalTradition |
P3466
|
FINISHED |
| Object | Anglicanism |
—
|
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: Anglicanism | Statement: [Diocese of Coventry, hasDenominationalTradition, Anglicanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDenominationalTradition Context triple: [Diocese of Coventry, hasDenominationalTradition, Anglicanism]
-
A.
hasRiteOrTradition
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
B.
theologicalTradition
chosen
Indicates the religious or doctrinal school, lineage, or system of belief within which an entity’s theology is developed or practiced.
-
C.
hasDenominationalVariation
Indicates that there are differing forms, practices, or interpretations of something across distinct denominations or sects.
-
D.
hasDenominationalHead
Indicates that an organization or religious body is led or overseen by a specific denominational head or leader.
-
E.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be0370b4819093618930f4eecfcc |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.