Triple
T28159484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Спасо-Преображенский монастырь |
E714849
|
entity |
| Predicate | религиознаяФункция |
P2330
|
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.
religiousFunction
chosen
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
-
B.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
E.
regionReligiousRole
Indicates the role or function that religion plays within a particular region, such as its religious status, significance, or designated religious purpose.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641e9eac08190976874fc569b4a63 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:05 p.m.