Triple
T36406615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Церковь Святого Архангела Михаила |
E896763
|
entity |
| Predicate | имеет небесного покровителя |
P92826
|
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.
почитает небесного покровителя
Indicates that one entity shows reverence or devotion to a heavenly patron or protector.
-
B.
spiritualPatron
Indicates that one entity serves as a guiding or protective spiritual figure or patron for another entity.
-
C.
hasGuardianDeity
chosen
Indicates that an entity is under the protection or patronage of a specific guardian deity.
-
D.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
E.
isBelovedOf
Indicates that one entity is deeply loved, cherished, or held in special affection by 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.