Triple
T4757770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | terza rima |
E105628
|
entity |
| Predicate | hasFunctionInDivineComedy |
P58312
|
FINISHED |
| Object | organizing large-scale narrative |
—
|
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: organizing large-scale narrative | Statement: [terza rima, hasFunctionInDivineComedy, organizing large-scale narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionInDivineComedy Context triple: [terza rima, hasFunctionInDivineComedy, organizing large-scale narrative]
-
A.
hasSacredFunction
Indicates that something serves a religious or holy role, purpose, or duty within a sacred context.
-
B.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
C.
hasMythicFunction
Indicates that something serves a symbolic, narrative, or ritual role within a mythic or mythological framework.
-
D.
hasMythologicalFeature
Indicates that an entity possesses a characteristic, attribute, or element derived from mythology or mythological beings.
-
E.
allegoricalRoleInInferno
Indicates a symbolic or allegorical function that an entity fulfills within the narrative framework of Dante’s Inferno.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.