Triple
T19687692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Purgatory |
E472753
|
entity |
| Predicate | firstCantoNumberInPurgatorio |
P58300
|
FINISHED |
| Object | Canto I |
—
|
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: Canto I | Statement: [Mount Purgatory, firstCantoNumberInPurgatorio, Canto I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCantoNumberInPurgatorio Context triple: [Mount Purgatory, firstCantoNumberInPurgatorio, Canto I]
-
A.
firstCantoNumberingNote
chosen
Indicates the note that explains how the numbering of the first canto is handled or interpreted.
-
B.
guideInInfernoAndPurgatorio
Indicates that one entity serves as a guide to another within both the Inferno and Purgatorio sections of Dante’s Divine Comedy.
-
C.
numberOfCantos
Indicates the total count of cantos associated with a given work or entity.
-
D.
firstTwoCantosPublished
Indicates that the first two cantos of a larger poetic or literary work have been formally released or made publicly available.
-
E.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.