Triple
T4879117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Phlegethon |
E109280
|
entity |
| Predicate | afterlifeAssociation |
P48829
|
FINISHED |
| Object | realm of the damned |
—
|
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: realm of the damned | Statement: [River Phlegethon, afterlifeAssociation, realm of the damned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterlifeAssociation Context triple: [River Phlegethon, afterlifeAssociation, realm of the damned]
-
A.
associatedAfterlife
chosen
Indicates a relationship where an entity is linked to, or characterized by, a particular concept, realm, or state of existence after death.
-
B.
afterlifeFate
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
-
C.
afterlifeForm
Indicates the form, state, or manifestation an entity takes in an afterlife or post-mortem existence.
-
D.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
E.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
- 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.