Triple
T12480451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayar Cachi |
E298288
|
entity |
| Predicate | causeOfBetrayal |
P105231
|
FINISHED |
| Object | fear of his strength |
—
|
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: fear of his strength | Statement: [Ayar Cachi, causeOfBetrayal, fear of his strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfBetrayal Context triple: [Ayar Cachi, causeOfBetrayal, fear of his strength]
-
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.
betrayalSign
Indicates an action or signal through which one party violates the trust, loyalty, or expectations of another.
-
C.
causeOfVengeance
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e87e0e88190bc49dcfe4954c7e0 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:56 p.m.