Triple
T31977714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ixion |
E816491
|
entity |
| Predicate | eternalPunishment |
P122930
|
FINISHED |
| Object | wheel whirling through the air |
—
|
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: wheel whirling through the air | Statement: [Ixion, eternalPunishment, wheel whirling through the air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eternalPunishment Context triple: [Ixion, eternalPunishment, wheel whirling through the air]
-
A.
punishedInAfterlife
Indicates that an entity is subjected to punishment or negative consequences in an afterlife or post-mortem realm.
-
B.
isEternal
Indicates that something exists without beginning or end, persisting indefinitely through all time.
-
C.
timeOfCondemnation
Indicates the specific time at which a condemnation (such as a legal judgment or formal denunciation) occurs or is issued.
-
D.
condemnedTo
chosen
Indicates that one entity has been sentenced or assigned by another entity to undergo a specific punishment, usually involving severe or irreversible consequences.
-
E.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34672f08190bd219f937ce6b1dd |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.