Triple
T36500065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Kuntsevych |
E899298
|
entity |
| Predicate | hasCanonizationDate |
P201060
|
FINISHED |
| Object | 1867 |
—
|
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: 1867 | Statement: [Ivan Kuntsevych, hasCanonizationDate, 1867]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonizationDate Context triple: [Ivan Kuntsevych, hasCanonizationDate, 1867]
-
A.
hasCanonization
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
-
B.
hasPartInCanonizationStatus
Indicates that an entity participates in or contributes to determining another entity’s canonization status.
-
C.
canonizedDuring
Indicates that an individual was officially declared a saint during a specified time period or under a particular authority.
-
D.
hasCanonicalCoronationStatus
Indicates that an entity has an officially recognized or standard status with respect to a coronation.
-
E.
hasPartInCanonization
Indicates that an entity participated in or contributed to the process of canonization of another entity.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: May 3, 2026, 4:10 p.m.