Triple
T19322768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melot |
E483267
|
entity |
| Predicate | betrayalType |
P135610
|
FINISHED |
| Object | personal betrayal |
—
|
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: personal betrayal | Statement: [Melot, betrayalType, personal betrayal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betrayalType Context triple: [Melot, betrayalType, personal betrayal]
-
A.
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.
-
B.
causeOfBetrayal
Indicates that one entity is the reason or motivating factor behind another entity’s act of betrayal.
-
C.
betrayalSign
Indicates an action or signal through which one party violates the trust, loyalty, or expectations of another.
-
D.
betrayalLocation
Indicates the place where an act of betrayal occurs or is carried out.
-
E.
betrayalReward
Indicates that an entity receives a benefit or compensation as a direct result of betraying another party or prior allegiance.
- F. None of above. chosen
Provenance (4 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8948948190b76a384041333509 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.