Triple
T23244613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Proetus |
E581550
|
entity |
| Predicate | causeOfDaughtersMadness |
P694
|
FINISHED |
| Object | offense against Hera (in some versions) |
—
|
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: offense against Hera (in some versions) | Statement: [King Proetus, causeOfDaughtersMadness, offense against Hera (in some versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDaughtersMadness Context triple: [King Proetus, causeOfDaughtersMadness, offense against Hera (in some versions)]
-
A.
causeOfDaughterDeaths
Indicates a relationship where an entity is the cause or reason for the deaths of one or more daughters.
-
B.
causeStatedByPerpetrators
Indicates that the stated cause or reason for an event or action is the one explicitly given by the perpetrators themselves.
-
C.
causeOfMothersDeath
Indicates that the subject is the specific cause responsible for the mother’s death.
-
D.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
raisesAsDaughter
Indicates that one entity brings up and cares for another as their daughter, in a parental role.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.