Triple
T790512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory of Nyssa |
E16902
|
entity |
| Predicate | appointedAsBishop |
P8553
|
FINISHED |
| Object | c. 372 |
—
|
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: c. 372 | Statement: [Gregory of Nyssa, appointedAsBishop, c. 372]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsBishop Context triple: [Gregory of Nyssa, appointedAsBishop, c. 372]
-
A.
appointedAuxiliaryBishop
Indicates that one entity formally assigns another to serve in the role of auxiliary bishop within a diocese or ecclesiastical jurisdiction.
-
B.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
D.
electedAsPresidingBishopOn
Indicates that an individual was chosen and formally appointed to serve as Presiding Bishop on a specific date.
-
E.
appointedAs
chosen
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79754988190ab494b1c54d6a2a4 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.