Triple
T8807734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodoxy or Death |
E209575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orthodox Christian slogan |
C9364
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Orthodox Christian slogan Context triple: [Orthodoxy or Death, instanceOf, Orthodox Christian slogan]
-
A.
Eastern Orthodox Christian
An Eastern Orthodox Christian is a follower of the Eastern Orthodox Church who adheres to its ancient liturgical traditions, theology, and spiritual practices centered on the Holy Trinity, the sacraments, and the continuity of the early Christian faith.
-
B.
religious slogan
chosen
A religious slogan is a short, memorable phrase that expresses and promotes a core belief, value, or message of a faith tradition.
-
C.
Orthodox Christian institution
An Orthodox Christian institution is an organized body, such as a church, monastery, or educational center, that preserves, practices, and transmits the faith, worship, and traditions of Eastern Orthodox Christianity within a structured communal framework.
-
D.
Eastern Orthodox church
An Eastern Orthodox church is a Christian place of worship characterized by its adherence to Eastern Orthodox theology and liturgy, often featuring domes, icons, and a richly decorated interior focused on the Divine Liturgy.
-
E.
Russian Orthodox church
A Russian Orthodox church is a Christian religious building belonging to the Russian Orthodox tradition, characterized by its distinctive onion domes, iconostasis, and liturgical practices rooted in Eastern Orthodoxy.
- F. None of above.
Provenance (1 batch)
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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:45 p.m.