Triple
T18639452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John X of Antioch |
E455642
|
entity |
| Predicate | consecrationAsPatriarch |
P92208
|
FINISHED |
| Object | 2012-12-23 |
—
|
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: 2012-12-23 | Statement: [John X of Antioch, consecrationAsPatriarch, 2012-12-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecrationAsPatriarch Context triple: [John X of Antioch, consecrationAsPatriarch, 2012-12-23]
-
A.
enthronedAsPatriarch
chosen
Indicates that an individual has been formally installed or elevated to the office and authority of a patriarch.
-
B.
electedAsPatriarch
Indicates that an entity has been chosen or appointed to hold the position or office of patriarch.
-
C.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
D.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
E.
consecratedBishopOn
Indicates that one entity performed the act of consecrating another entity as a bishop on a specific date or occasion.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fcbe3088190849f60b09d1e7e4b |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.