Triple
T22557334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Althaemenes |
E557721
|
entity |
| Predicate | circumstancesOfPatricide |
P34163
|
FINISHED |
| Object | mistook his father for a raider landing on Rhodes |
—
|
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: mistook his father for a raider landing on Rhodes | Statement: [Althaemenes, circumstancesOfPatricide, mistook his father for a raider landing on Rhodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circumstancesOfPatricide Context triple: [Althaemenes, circumstancesOfPatricide, mistook his father for a raider landing on Rhodes]
-
A.
sisterMurdered
Indicates that one entity killed the sister of another entity.
-
B.
reasonForMurder
chosen
Indicates the motive or underlying cause that led someone to commit a murder.
-
C.
killedFamilyOf
Indicates that one entity caused the death of one or more members of another entity’s family.
-
D.
persecutorOfMother
Indicates that one entity persecutes, harasses, or oppresses another entity who is the mother of someone.
-
E.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented 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_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.