Triple
T27304617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail of Tver |
E689016
|
entity |
| Predicate | canonizationReason |
P25961
|
FINISHED |
| Object | martyrdom |
—
|
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: martyrdom | Statement: [Mikhail of Tver, canonizationReason, martyrdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonizationReason Context triple: [Mikhail of Tver, canonizationReason, martyrdom]
-
A.
canonizationType
Indicates the specific manner or category by which an individual is formally recognized as a saint or holy figure within a religious canon.
-
B.
reasonForCanonization
chosen
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
C.
canonizationDate
Indicates the date on which an individual was officially declared a saint (canonized) by a religious authority.
-
D.
canonizationName
Indicates the official name or title conferred upon an individual as part of their canonization.
-
E.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11:24 a.m.