Triple
T4956235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphinx |
E111286
|
entity |
| Predicate | punishmentForFailure |
P3012
|
FINISHED |
| Object | death of those who fail her riddle |
—
|
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: death of those who fail her riddle | Statement: [Sphinx, punishmentForFailure, death of those who fail her riddle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: punishmentForFailure Context triple: [Sphinx, punishmentForFailure, death of those who fail her riddle]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
reasonForPunishment
Indicates that one entity is the cause, justification, or grounds for another entity receiving a punishment.
-
C.
aimOfPunishment
Indicates that a specified purpose or objective is the intended goal or rationale behind a particular act of punishment.
-
D.
hasPunishment
chosen
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
-
E.
punishmentLocation
Indicates the place or setting where a punishment is carried out or imposed.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.