Triple
T4879109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Phlegethon |
E109280
|
entity |
| Predicate | functionInMyth |
P49015
|
FINISHED |
| Object | torments the souls of the wicked |
—
|
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: torments the souls of the wicked | Statement: [River Phlegethon, functionInMyth, torments the souls of the wicked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInMyth Context triple: [River Phlegethon, functionInMyth, torments the souls of the wicked]
-
A.
hasMythicFunction
chosen
Indicates that something serves a symbolic, narrative, or ritual role within a mythic or mythological framework.
-
B.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
C.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
D.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
-
E.
functionInPractice
Indicates that an entity serves a particular role or performs a specific function in actual use or real-world practice.
- 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.