Triple
T5188931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Tempters |
E117100
|
entity |
| Predicate | allegoricalLevel |
P24039
|
FINISHED |
| Object | psychological forces |
—
|
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: psychological forces | Statement: [Four Tempters, allegoricalLevel, psychological forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegoricalLevel Context triple: [Four Tempters, allegoricalLevel, psychological forces]
-
A.
allegoricalDomain
Indicates that one entity serves as the abstract or symbolic domain that another entity allegorically represents or refers to.
-
B.
hasAllegoricalFigures
chosen
Indicates that a work, scene, or element includes figures that symbolically represent abstract ideas, concepts, or moral qualities.
-
C.
politicalAllegoryFor
Indicates that one entity symbolically represents or critiques another entity, event, or system within a political context.
-
D.
logicalLevel
Indicates the relative position or depth of something within a hierarchy of abstraction, reasoning, or logical structure.
-
E.
allegoricalRoleInInferno
Indicates a symbolic or allegorical function that an entity fulfills within the narrative framework of Dante’s Inferno.
- 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_69bd44620ff48190bcac01782107a397 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c732b48190af62dfffcbc5e3a6 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:46 p.m.