Triple
T18191118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theophilos III of Jerusalem |
E435534
|
entity |
| Predicate | electionAsPatriarch |
P44068
|
FINISHED |
| Object | 2005-08-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: 2005-08-22 | Statement: [Theophilos III of Jerusalem, electionAsPatriarch, 2005-08-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionAsPatriarch Context triple: [Theophilos III of Jerusalem, electionAsPatriarch, 2005-08-22]
-
A.
electionAsPatriarchDate
chosen
Indicates the date on which an individual was formally elected to the position of patriarch.
-
B.
electionOfHead
Indicates the process or event in which a person is chosen or appointed to serve as the head or leader of an organization, group, or entity.
-
C.
electedAsPatriarch
Indicates that an entity has been chosen or appointed to hold the position or office of patriarch.
-
D.
executiveElectedBy
Indicates that an executive assumes office as a result of being chosen through a formal election conducted by a specified person, group, or body.
-
E.
papalElection
Indicates the process or event in which a new pope is chosen and formally elected to the papal office.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0cf0d7c81908ce0386c52ef601d |
completed | April 19, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.