Triple
T20872415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eriphyle |
E513926
|
entity |
| Predicate | betrayalInstrument |
P25016
|
FINISHED |
| Object | acceptance of Polynices’ bribe |
—
|
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: acceptance of Polynices’ bribe | Statement: [Eriphyle, betrayalInstrument, acceptance of Polynices’ bribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betrayalInstrument Context triple: [Eriphyle, betrayalInstrument, acceptance of Polynices’ bribe]
-
A.
betrayalType
Indicates the specific kind or category of betrayal that characterizes the relationship or action between the involved entities.
-
B.
betrayalSign
Indicates an action or signal through which one party violates the trust, loyalty, or expectations of another.
-
C.
betrayed
Indicates that one entity has broken the trust, loyalty, or confidence of another, typically by acting against their interests or revealing something meant to be kept secret.
-
D.
betrayalReward
chosen
Indicates that an entity receives a benefit or compensation as a direct result of betraying another party or prior allegiance.
-
E.
betrayalLocation
Indicates the place where an act of betrayal occurs or is carried out.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c465693881909fe4c756ddc4f291 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.