Triple
T37934695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordva |
E946313
|
entity |
| Predicate | mainReligionToday |
P52189
|
FINISHED |
| Object | Eastern Orthodoxy |
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 Orthodoxy | Statement: [Mordva, mainReligionToday, Eastern Orthodoxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainReligionToday Context triple: [Mordva, mainReligionToday, Eastern Orthodoxy]
-
A.
subjectReligion
chosen
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
B.
modernReligionMix
Indicates a relationship where elements from multiple religious traditions are combined or blended into a contemporary, syncretic religious practice or identity.
-
C.
contemporaryReligion
Indicates that two entities practice or are associated with religions that exist and are followed during the same historical time period.
-
D.
religionCommon
Indicates that the related entities share the same religion or religious affiliation.
-
E.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117f159008190a07ccc46cc3a3f15 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.