Triple
T37843962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Falke |
E943551
|
entity |
| Predicate | reasonForRevenge |
P61789
|
FINISHED |
| Object | previous humiliation by Gabriel von Eisenstein |
—
|
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: previous humiliation by Gabriel von Eisenstein | Statement: [Dr. Falke, reasonForRevenge, previous humiliation by Gabriel von Eisenstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRevenge Context triple: [Dr. Falke, reasonForRevenge, previous humiliation by Gabriel von Eisenstein]
-
A.
causeOfVengeance
chosen
Indicates a relationship where one entity is the reason or trigger for another entity’s desire or act of vengeance.
-
B.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
C.
reasonForDuel
Indicates the cause, motive, or triggering circumstance that led to the duel between the involved parties.
-
D.
reasonForDefiance
Indicates the underlying cause or motivation that leads an entity to resist, oppose, or disobey another entity or directive.
-
E.
causeOfResentment
Indicates that one entity is the source or reason for another entity’s feeling of resentment.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:19 p.m.