Triple
T22557333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Althaemenes |
E557721
|
entity |
| Predicate | mannerOfKillingFather |
P2115
|
FINISHED |
| Object | struck Catreus with a spear |
—
|
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: struck Catreus with a spear | Statement: [Althaemenes, mannerOfKillingFather, struck Catreus with a spear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mannerOfKillingFather Context triple: [Althaemenes, mannerOfKillingFather, struck Catreus with a spear]
-
A.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
B.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
C.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
-
D.
usedMethodOfKilling
chosen
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
E.
killedFamilyOf
Indicates that one entity caused the death of one or more members of another entity’s family.
- 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_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. |
Created at: April 16, 2026, 8:52 p.m.