Triple
T25364638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessed |
E636065
|
entity |
| Predicate | rankInCanonization |
P20537
|
FINISHED |
| Object | third step |
—
|
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: third step | Statement: [Blessed, rankInCanonization, third step]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInCanonization Context triple: [Blessed, rankInCanonization, third step]
-
A.
rankInRomanCatholicChurch
Indicates that one entity holds a specific hierarchical or clerical position within the structure of the Roman Catholic Church in relation to another entity.
-
B.
inCanonizationStatus
chosen
Indicates that an entity has a specific status or stage within a formal canonization process.
-
C.
rankInPapalOrders
Indicates the relative hierarchical position or level an entity holds within the structure of papal orders.
-
D.
canonizedIn
Indicates that an authority formally declared someone to be a saint or holy figure in a specified place or institution.
-
E.
canonizationType
Indicates the specific manner or category by which an individual is formally recognized as a saint or holy figure within a religious canon.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 1:36 p.m.