Triple
T36406604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Церковь Святого Архангела Михаила |
E896763
|
entity |
| Predicate | почитает небесного покровителя |
P185452
|
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.
divineProtection
Indicates a relationship where one entity safeguards, blesses, or shields another through supernatural or sacred power.
-
B.
تذكر كتاب الأبرار
Indicates that an entity recalls or mentions the book of the righteous.
-
C.
تصف الملائكة
Indicates a relationship where a subject describes or portrays angels in some manner.
-
D.
حكم تلاوتها
Indicates the ruling or legal judgment regarding the recitation of something (e.g., whether its recitation is obligatory, recommended, permissible, disliked, or forbidden).
-
E.
נקראים
Indicates that entities are named, called, or referred to by a particular term or title.
- F. None of above. chosen
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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.