Triple
T21178207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confession of Cyril Lucaris |
E521870
|
entity |
| Predicate | positionOnPredestination |
P143173
|
FINISHED |
| Object | affirms unconditional election |
—
|
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: affirms unconditional election | Statement: [Confession of Cyril Lucaris, positionOnPredestination, affirms unconditional election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnPredestination Context triple: [Confession of Cyril Lucaris, positionOnPredestination, affirms unconditional election]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
C.
positionOnPast
Indicates that one entity occupied a specific position or location relative to another entity at some point in the past.
-
D.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
E.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301b41908190bc104aa748a0346d |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3 p.m.