Triple
T30195727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhny Novgorod Eparchy |
E767623
|
entity |
| Predicate | mainReligionOfMembers |
P2986
|
FINISHED |
| Object | Russian Orthodox Christianity |
—
|
NE NERFINISHED |
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: Russian Orthodox Christianity | Statement: [Nizhny Novgorod Eparchy, mainReligionOfMembers, Russian Orthodox Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReligionOfMembers Context triple: [Nizhny Novgorod Eparchy, mainReligionOfMembers, Russian Orthodox Christianity]
-
A.
dominantReligion
chosen
Indicates the religion that holds primary or majority status within a given group, region, or entity.
-
B.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
C.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
D.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
E.
mainAdherents
Indicates the primary group or groups that predominantly follow, support, or adhere to something (such as a belief, movement, or organization).
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f86de74819091cb45049fb9e1f8 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:29 p.m.