Triple
T26687016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiope |
E672773
|
entity |
| Predicate | vengeanceTakenOn |
P61789
|
FINISHED |
| Object | Dirce |
—
|
NE NERFINISHED |
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: Dirce | Statement: [Antiope, vengeanceTakenOn, Dirce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vengeanceTakenOn Context triple: [Antiope, vengeanceTakenOn, Dirce]
-
A.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
B.
causeOfVengeance
chosen
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
C.
avenges
Indicates that one entity retaliates or exacts retribution against another entity on behalf of a wrong or harm done to a third party.
-
D.
محاكمة
Indicates that a legal trial or judicial proceeding is being conducted involving the entities.
-
E.
victimHeirTo
Indicates that the victim is the legal heir or inheritor of another person involved in the event or relationship.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173f709881909da3e62baa6c9781 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:23 a.m.