Triple
T22144821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartholomew I of Constantinople |
E547257
|
entity |
| Predicate | electedAsEcumenicalPatriarchOn |
P71269
|
FINISHED |
| Object | 1991-10-22 |
—
|
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: 1991-10-22 | Statement: [Bartholomew I of Constantinople, electedAsEcumenicalPatriarchOn, 1991-10-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electedAsEcumenicalPatriarchOn Context triple: [Bartholomew I of Constantinople, electedAsEcumenicalPatriarchOn, 1991-10-22]
-
A.
electedAsEcumenicalPatriarch
chosen
Indicates that an individual has been chosen and formally appointed to serve as the Ecumenical Patriarch.
-
B.
electedAsPatriarch
Indicates that an entity has been chosen or appointed to hold the position or office of patriarch.
-
C.
electedAsPresidingBishopOn
Indicates that an individual was chosen and formally appointed to serve as Presiding Bishop on a specific date.
-
D.
electedAsArchbishopOn
Indicates that an entity was chosen and formally appointed to the position of archbishop on a specific date.
-
E.
electedAsPopeIn
Indicates that an individual was chosen and formally installed as Pope in a specific year or at a specific time.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129efd52c8190ab0acff5bbfc0d77 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.