Triple
T31413330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of the Russian Empire |
E801325
|
entity |
| Predicate | typicalBearerReligion |
P81268
|
FINISHED |
| Object | Eastern Orthodox Christianity |
E398
|
NE 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: Eastern Orthodox Christianity | Statement: [Count of the Russian Empire, typicalBearerReligion, Eastern Orthodox Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBearerReligion Context triple: [Count of the Russian Empire, typicalBearerReligion, Eastern Orthodox Christianity]
-
A.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
B.
hasReligiousType
Indicates that an entity is associated with or classified under a particular religion or religious category.
-
C.
majorReligionCanBe
chosen
Indicates that an entity can have a particular major religion as one of its possible primary religious affiliations.
-
D.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
E.
namedForPersonReligion
Indicates that something is named after a person specifically because of that person's religious identity, role, or significance.
- F. None of above.
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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b1440c82081909e09b11ef444b9ff |
completed | June 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:41 p.m.