Triple
T785111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian Orthodox Church |
E16583
|
entity |
| Predicate | schismEndDate |
P19603
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Bulgarian Orthodox Church, schismEndDate, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schismEndDate Context triple: [Bulgarian Orthodox Church, schismEndDate, 1945]
-
A.
excommunicationDate
Indicates the date on which an individual or entity was formally excommunicated from a religious community or institution.
-
B.
dateOfMutualExcommunications
Indicates the date on which two parties formally issued excommunications against each other.
-
C.
excommunicationYear
Indicates the year in which an entity was formally excommunicated from a religious community or institution.
-
D.
wasDividedFromYear
Indicates that an entity began to be separated or partitioned starting from a specified year.
-
E.
churchSplitWith
Indicates that a church or religious congregation has divided into separate groups or factions, often due to doctrinal, organizational, or interpersonal conflicts, in relation to another specified church or group.
- F. None of above. chosen
Provenance (4 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a76b0d6c8190a09b1a0bd4a6eeec |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a67e69288190b3dc278c5bd94155 |
completed | March 1, 2026, 8:50 p.m. |
Created at: March 1, 2026, 7:37 p.m.