Triple
T28774380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Felix III |
E726493
|
entity |
| Predicate | schismInvolved |
P107689
|
FINISHED |
| Object | Acacian Schism |
—
|
NE NERFINISHED |
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: Acacian Schism | Statement: [Pope Felix III, schismInvolved, Acacian Schism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schismInvolved Context triple: [Pope Felix III, schismInvolved, Acacian Schism]
-
A.
associatedSchism
chosen
Indicates a relationship where one entity is linked to, or involved in, a particular schism or split within a group, organization, or movement.
-
B.
schismEndDate
Indicates the date on which a schism, split, or formal division between parties came to an end.
-
C.
causeOfSchism
Indicates that one entity is the reason or primary factor leading to a division or split between groups, typically in a religious, organizational, or ideological context.
-
D.
majorSchism
Indicates a significant and formal split or division between previously unified groups, organizations, or factions.
-
E.
opponentInSchism
Indicates that two parties stand on opposing sides within the same internal division, dispute, or schismatic conflict.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:17 a.m.