Triple
T10238637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus Tolton |
E243531
|
entity |
| Predicate | yearCauseForCanonizationOpened |
P92917
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Augustus Tolton, yearCauseForCanonizationOpened, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearCauseForCanonizationOpened Context triple: [Augustus Tolton, yearCauseForCanonizationOpened, 2010]
-
A.
canonizationDate
Indicates the date on which an individual was officially declared a saint (canonized) by a religious authority.
-
B.
dateOfCanonizationStatus
Indicates the date on which an entity’s canonization status (such as being declared a saint or blessed) was formally conferred or recorded.
-
C.
reasonForCanonization
Indicates the specific cause, miracle, virtue, or event that served as the basis for a person’s canonization.
-
D.
inCanonizationStatus
Indicates that an entity has a specific status or stage within a formal canonization process.
-
E.
beatificationDate
Indicates the date on which a person was officially declared blessed (beatified) in a religious context.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:23 a.m.