Triple
T36406603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Церковь Святого Архангела Михаила |
E896763
|
entity |
| Predicate | является типом |
P163135
|
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.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
InType
chosen
Indicates that an entity belongs to, is categorized under, or is an instance of a specified type or class.
-
C.
introducedAsType
Indicates that one entity is presented or identified to others as having a particular role, category, or type.
-
D.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
-
E.
checkingType
Indicates that one entity is verifying, inspecting, or assessing the type or category of 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_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.