Triple
T31301687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Did Something Bad |
E798228
|
entity |
| Predicate | hasRevengeNarrative |
P175382
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [I Did Something Bad, hasRevengeNarrative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevengeNarrative Context triple: [I Did Something Bad, hasRevengeNarrative, true]
-
A.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
B.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
C.
hasVengefulTone
chosen
Indicates that the subject expresses anger, resentment, or a desire for revenge toward another entity in its tone or manner.
-
D.
hasNarrativeArcOf
Indicates that one entity embodies, represents, or corresponds to the narrative arc (story progression or plot structure) of another entity.
-
E.
hasNarrativeEvent
Indicates that one entity includes, contains, or is associated with a specific narrative event within a story or sequence of events.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: April 29, 2026, 9:14 p.m.