Triple
T665100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | See of Canterbury |
E12842
|
entity |
| Predicate | hasGlobalRole |
P17793
|
FINISHED |
| Object | focus of unity for the Anglican Communion |
—
|
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: focus of unity for the Anglican Communion | Statement: [See of Canterbury, hasGlobalRole, focus of unity for the Anglican Communion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlobalRole Context triple: [See of Canterbury, hasGlobalRole, focus of unity for the Anglican Communion]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasRegionalRole
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
-
C.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
D.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd3d8fc8190866af5c76c08f486 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d16cff881908c8d2c3fe4d1d6fb |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49df0de3c81909721eb391ec94031 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:36 p.m.