Triple
T20710680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanov family canonization |
E509027
|
entity |
| Predicate | basisForCanonization |
P25961
|
FINISHED |
| Object | pious conduct |
—
|
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: pious conduct | Statement: [Romanov family canonization, basisForCanonization, pious conduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisForCanonization Context triple: [Romanov family canonization, basisForCanonization, pious conduct]
-
A.
reasonForCanonization
chosen
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
B.
canonizedBy
Indicates that an entity has been officially declared a saint or holy figure by a specified religious authority.
-
C.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
D.
canonizationType
Indicates the specific manner or category by which an individual is formally recognized as a saint or holy figure within a religious canon.
-
E.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1974ba08190b0e5ad529be95e4c |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.