Triple
T36406636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Церковь Святого Архангела Михаила |
E896763
|
entity |
| Predicate | относится к типу святыни |
P186429
|
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.
venerationType
Indicates the specific manner or category of reverence or worship directed toward an entity.
-
B.
reliquaryType
Indicates the specific kind or category of reliquary associated with an entity.
-
C.
veneratedSaintRelicsEnshrined
Indicates that the relics of a venerated saint are formally enshrined or housed in a particular place or container.
-
D.
typeOfSaint
Indicates that one entity is classified as a specific kind or category of saint in relation to another entity.
-
E.
associatedReligionForRelic
Indicates the religion with which a particular relic is associated.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:10 p.m.