Triple
T20773179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bias |
E511287
|
entity |
| Predicate | avenge |
P66625
|
FINISHED |
| Object | his father’s defeat at Thebes |
—
|
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: his father’s defeat at Thebes | Statement: [Bias, avenge, his father’s defeat at Thebes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avenge Context triple: [Bias, avenge, his father’s defeat at Thebes]
-
A.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
B.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
C.
bloodlust
Indicates an intense, often uncontrollable desire to shed blood or commit violent harm.
-
D.
avenges
chosen
Indicates that one entity retaliates or exacts retribution against another entity on behalf of a wrong or harm done to a third party.
-
E.
ancrage
Indicates a relationship where one entity is anchored, fixed, or firmly attached to another entity, serving as a stable point of support or reference.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c269638881909d96b847f7de5585 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.