Triple
T20418337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Rich |
E500772
|
entity |
| Predicate | relativeHasCanonizationStatus |
P54357
|
FINISHED |
| Object | saint |
—
|
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: saint | Statement: [Robert Rich, relativeHasCanonizationStatus, saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHasCanonizationStatus Context triple: [Robert Rich, relativeHasCanonizationStatus, saint]
-
A.
hasCanonization
chosen
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
-
B.
hasPartInCanonization
Indicates that an entity participated in or contributed to the process of canonization of another entity.
-
C.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
D.
typeOfCanonization
Indicates the specific form or category of canonization by which an entity was officially declared sacred or recognized as a saint.
-
E.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a4686a48190a808c86aa916ad56 |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.