Triple
T32389699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | основной культ |
P7648
|
FINISHED |
| Object | почитание Святой Троицы |
—
|
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: почитание Святой Троицы | Statement: [Белая Троицкая церковь, основной культ, почитание Святой Троицы]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: основной культ Context triple: [Белая Троицкая церковь, основной культ, почитание Святой Троицы]
-
A.
mainDeity
chosen
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
mainFaith
Indicates that one entity is the primary or predominant religious belief or faith tradition associated with another entity.
-
C.
dominantReligion
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
D.
laterReligionDominant
Indicates that a religion adopted or followed at a later time becomes the dominant or primary religion in the relevant context or entity.
-
E.
الديانة
Indicates the religious affiliation or faith tradition that an entity follows or is associated with.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1d48d048190b6bb79e26881adb7 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:52 a.m.