Triple
T28159476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Спасо-Преображенский монастырь |
E714849
|
entity |
| Predicate | имеетОбъектПоклонения |
P128939
|
FINISHED |
| Object | храм Преображения Господня |
—
|
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: храм Преображения Господня | Statement: [Спасо-Преображенский монастырь, имеетОбъектПоклонения, храм Преображения Господня]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетОбъектПоклонения Context triple: [Спасо-Преображенский монастырь, имеетОбъектПоклонения, храм Преображения Господня]
-
A.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
B.
isAdmiredBy
Indicates that one entity holds admiration or high regard for another entity.
-
C.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by another entity.
-
D.
hasReligiousObject
chosen
Indicates that an entity possesses, is associated with, or contains a religious object (such as an artifact, symbol, or item used in religious practice).
-
E.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:05 p.m.