Triple
T36951978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Canterbury |
E914088
|
entity |
| Predicate | communionHeadOf |
P46547
|
FINISHED |
| Object | Anglican Communion |
—
|
NE NERFINISHED |
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 Communion | Statement: [Bishop of Canterbury, communionHeadOf, Anglican Communion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communionHeadOf Context triple: [Bishop of Canterbury, communionHeadOf, Anglican Communion]
-
A.
communionHead
chosen
Indicates that one entity serves as the leading or governing authority over a religious communion or church body in relation to another entity.
-
B.
communion
Indicates a close, often spiritual or emotional sharing or union between entities.
-
C.
communionWith
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
D.
communionDeclared
Indicates that an official statement has been made affirming or recognizing a state of religious or spiritual communion between the involved parties.
-
E.
areLedInCommunionWith
Indicates that one group or individual is guided or governed in a shared religious or spiritual union with another.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.