Triple
T5304940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church on the Blood in Yekaterinburg |
E120075
|
entity |
| Predicate | hasRelicType |
P63949
|
FINISHED |
| Object | place associated with relics and memory of the Romanovs |
—
|
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: place associated with relics and memory of the Romanovs | Statement: [Church on the Blood in Yekaterinburg, hasRelicType, place associated with relics and memory of the Romanovs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelicType Context triple: [Church on the Blood in Yekaterinburg, hasRelicType, place associated with relics and memory of the Romanovs]
-
A.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
B.
hasRelicsStatus
Indicates that an entity holds a particular status or condition specifically related to relics.
-
C.
hasHeirloom
Indicates that one entity possesses or is associated with an heirloom originating from another entity.
-
D.
hasRitualType
Indicates that an entity is associated with, or classified by, a particular type or category of ritual.
-
E.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd8e43c4c88190bb72b9bf56c99425 |
completed | March 20, 2026, 6:13 p.m. |
Created at: March 20, 2026, 1:53 p.m.