Triple
T22557336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Althaemenes |
E557721
|
entity |
| Predicate | reactionToPatricide |
P148645
|
FINISHED |
| Object | overwhelmed with grief |
—
|
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: overwhelmed with grief | Statement: [Althaemenes, reactionToPatricide, overwhelmed with grief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactionToPatricide Context triple: [Althaemenes, reactionToPatricide, overwhelmed with grief]
-
A.
fatherReactionToDeath
Indicates the emotional or behavioral response of a father to the death of someone (typically a close relation).
-
B.
killedFamilyOf
Indicates that one entity caused the death of one or more members of another entity’s family.
-
C.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
D.
brothersKilledBy
Indicates that the referenced individuals are brothers who were killed by the same agent or in the same event.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- F. None of above. chosen
Provenance (4 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f7b06e08190b3ca82a783965942 |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:52 p.m.