Triple
T18639451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John X of Antioch |
E455642
|
entity |
| Predicate | ordainedAsBishop |
P14734
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [John X of Antioch, ordainedAsBishop, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordainedAsBishop Context triple: [John X of Antioch, ordainedAsBishop, 1995]
-
A.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
B.
wasOrdainedAs
chosen
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
appointedBishopOf
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
D.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
E.
ordainedIn
Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
- 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.