Triple
T27992943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matteo Ricci |
E706927
|
entity |
| Predicate | causeForCanonizationStatus |
P33854
|
FINISHED |
| Object | Servant of God |
—
|
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: Servant of God | Statement: [Matteo Ricci, causeForCanonizationStatus, Servant of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeForCanonizationStatus Context triple: [Matteo Ricci, causeForCanonizationStatus, Servant of God]
-
A.
causeForCanonizationOpenedBy
Indicates that an entity is the person or authority who formally initiated the cause for another entity’s canonization.
-
B.
reasonForCanonization
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
C.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
D.
hasCanonization
Indicates that an entity has undergone or been granted formal canonization, typically recognizing it as officially sainted or sanctified.
-
E.
canonicalStatusIn
chosen
Indicates that something has a particular canonical or officially recognized status within a specified 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 7:51 p.m.