Triple
T19901921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sixth Labour of Heracles |
E478311
|
entity |
| Predicate | commissionedAsPenanceFor |
P122934
|
FINISHED |
| Object | killing of Heracles’ family |
—
|
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: killing of Heracles’ family | Statement: [sixth Labour of Heracles, commissionedAsPenanceFor, killing of Heracles’ family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedAsPenanceFor Context triple: [sixth Labour of Heracles, commissionedAsPenanceFor, killing of Heracles’ family]
-
A.
performedPenanceAt
Indicates that an entity carried out an act of penance at a specific place or location.
-
B.
demandedAtonementFrom
chosen
Indicates that one entity required another to make amends or provide compensation for a perceived wrong or offense.
-
C.
repentsFor
Indicates that one entity feels remorse or regret for an action, wrongdoing, or harm related to another entity.
-
D.
soughtPardonFor
Indicates that one entity requested or attempted to obtain a formal pardon or forgiveness for another entity or for a specific action.
-
E.
punishedBy
Indicates that an entity receives punishment administered 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65943aefc81909e873e1845d5af3d |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.