Triple
T36581413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Святослав Шевчук |
E902404
|
entity |
| Predicate | підтвердження Римським Архиєреєм |
P62949
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Святослав Шевчук, підтвердження Римським Архиєреєм, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: підтвердження Римським Архиєреєм Context triple: [Святослав Шевчук, підтвердження Римським Архиєреєм, 2011]
-
A.
requiresPapalConfirmationFor
Indicates that one entity’s validity, effectiveness, or completion depends on receiving formal confirmation or approval from the Pope.
-
B.
papalApprovalBy
chosen
Indicates that an action, decision, or document has been formally approved or authorized by the Pope.
-
C.
appointedAsArchbishop
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
D.
recognizesAsSupremeBishop
Indicates that one party acknowledges and accepts another party as holding the highest episcopal or bishopric authority.
-
E.
ecclesiasticalRecognition
Indicates formal acknowledgment or approval granted by a religious or church authority to a person, group, status, or action.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.