Triple
T7979181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assumption Cathedral (Yaroslavl) |
E185521
|
entity |
| Predicate | reconsecrated |
P21434
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Assumption Cathedral (Yaroslavl), reconsecrated, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconsecrated Context triple: [Assumption Cathedral (Yaroslavl), reconsecrated, 2010]
-
A.
consecrated
chosen
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
-
B.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
C.
reproclaimed
Indicates that something was proclaimed or announced again, typically reaffirming or restating a previous declaration.
-
D.
consecratedInPresenceOf
Indicates that the act of consecration was performed while a specified person, group, or entity was present as a witness or participant.
-
E.
reopenedForWorship
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c261904819086910898071f3629 |
completed | March 31, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:14 p.m.