Triple
T24339455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Надежда |
E613472
|
entity |
| Predicate | религиозноКультурнаяСвязь |
P9028
|
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.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
B.
religiousOrRitualAssociation
Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
-
C.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
religiousInstitutionLinked
Indicates that there is an established connection or association between a religious institution and another entity.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932324e8819082344cf42eddc274 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.