Triple
T4879119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Phlegethon |
E109280
|
entity |
| Predicate | inDanteInferno |
P49606
|
FINISHED |
| Object | river of boiling blood and fire |
—
|
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: river of boiling blood and fire | Statement: [River Phlegethon, inDanteInferno, river of boiling blood and fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inDanteInferno Context triple: [River Phlegethon, inDanteInferno, river of boiling blood and fire]
-
A.
guideInInfernoAndPurgatorio
Indicates that one entity serves as a guide to another within both the Inferno and Purgatorio sections of Dante’s Divine Comedy.
-
B.
allegoricalRoleInInferno
chosen
Indicates a symbolic or allegorical function that an entity fulfills within the narrative framework of Dante’s Inferno.
-
C.
stateOfDevils
Indicates a condition, status, or situation specifically associated with devils.
-
D.
underFire
Indicates that an entity is being attacked, heavily criticized, or subjected to intense pressure by another entity or group.
-
E.
seventhStation
Indicates that one entity is the seventh stop, stage, or position in an ordered sequence of stations relative to another.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbf37ac819085bb758bc6406271 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.