Triple
T20778287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phineus |
E511410
|
entity |
| Predicate | tormentDescription |
P137929
|
FINISHED |
| Object | Harpies defiled his food |
—
|
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: Harpies defiled his food | Statement: [Phineus, tormentDescription, Harpies defiled his food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tormentDescription Context triple: [Phineus, tormentDescription, Harpies defiled his food]
-
A.
tormentsCharacter
chosen
Indicates that one entity causes ongoing psychological or physical suffering to another character.
-
B.
resultOfTorture
Indicates that something occurs as a direct consequence or outcome of an act of torture.
-
C.
torturedAt
Indicates that an entity was subjected to torture at a specific location or facility.
-
D.
useOfTorture
Indicates the intentional infliction or use of torture by one entity upon another, typically to punish, coerce, intimidate, or extract information.
-
E.
villainDescription
Indicates that one entity provides a description or characterization of a villainous role or antagonist associated with 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26d34bc81908bb22087d434322d |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.