Triple
T19888912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dioxippus |
E477976
|
entity |
| Predicate | causeOfEnmity |
P61068
|
FINISHED |
| Object | jealousy of Macedonian officers |
—
|
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: jealousy of Macedonian officers | Statement: [Dioxippus, causeOfEnmity, jealousy of Macedonian officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEnmity Context triple: [Dioxippus, causeOfEnmity, jealousy of Macedonian officers]
-
A.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
B.
hasCauseOfConflict
chosen
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
-
C.
reasonForAttack
Indicates that one entity’s attack on another is motivated or caused by the specified reason.
-
D.
causeOfBetrayal
Indicates that one entity is the reason or motivating factor behind another entity’s act of betrayal.
-
E.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.