Triple
T21973995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox monarchy |
E542658
|
entity |
| Predicate | stateChurchRelation |
P22562
|
FINISHED |
| Object | caesaropapism |
—
|
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: caesaropapism | Statement: [Russian Orthodox monarchy, stateChurchRelation, caesaropapism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateChurchRelation Context triple: [Russian Orthodox monarchy, stateChurchRelation, caesaropapism]
-
A.
churchStateRelation
chosen
Indicates the nature or degree of interaction, separation, or influence between religious institutions and governmental authority.
-
B.
isStateChurch
Indicates that a church is officially recognized and established as the state’s or government’s official religion.
-
C.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
-
D.
roleInStateReligion
Indicates that an entity holds a specific function, position, or involvement within the officially recognized religion of a state.
-
E.
stateChurchAssociationEnded
Indicates that a formal association or relationship between a state and a church has been terminated.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248668ac81909c74b2be62f69fce |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:02 p.m.