Triple
T37192187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paulinian party in Antioch |
E921485
|
entity |
| Predicate | schismType |
P107689
|
FINISHED |
| Object | episcopal schism |
—
|
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: episcopal schism | Statement: [Paulinian party in Antioch, schismType, episcopal schism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schismType Context triple: [Paulinian party in Antioch, schismType, episcopal 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.
majorSchism
Indicates a significant and formal split or division between previously unified groups, organizations, or factions.
-
D.
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.
-
E.
typeOfSynod
Indicates the specific kind or category to which a particular synod belongs.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.