Triple
T453725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primates’ Meeting |
E7185
|
entity |
| Predicate | consultsOn |
P13956
|
FINISHED |
| Object | Anglican Communion doctrine |
—
|
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 Communion doctrine | Statement: [Primates’ Meeting, consultsOn, Anglican Communion doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consultsOn Context triple: [Primates’ Meeting, consultsOn, Anglican Communion doctrine]
-
A.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
appointmentOnAdviceOf
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
-
C.
practiceType
Indicates the specific kind or category of practice associated with an entity or activity.
-
D.
endsOn
Indicates that one entity terminates or concludes precisely at the boundary or endpoint of another entity.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
- 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef866e848190a5b700250ec56256 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeeb85f881909580a6a86332b4a5 |
completed | Feb. 28, 2026, 1:34 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.