Triple
T11251884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daud |
E266337
|
entity |
| Predicate | feelsRemorseFor |
P35317
|
FINISHED |
| Object | assassination of Empress Jessamine Kaldwin |
—
|
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: assassination of Empress Jessamine Kaldwin | Statement: [Daud, feelsRemorseFor, assassination of Empress Jessamine Kaldwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feelsRemorseFor Context triple: [Daud, feelsRemorseFor, assassination of Empress Jessamine Kaldwin]
-
A.
contritionType
Indicates the specific kind or category of contrition (remorse or repentance) associated with an action or state.
-
B.
repentedIn
Indicates that an entity has expressed remorse or regret for its actions within a particular context, time, or situation.
-
C.
repentedTo
Indicates that one entity expressed remorse or sought forgiveness directly from another entity.
-
D.
laterRegretted
Indicates that an entity experienced regret at a later time about a prior action, decision, or state involving another entity.
-
E.
feels
chosen
Indicates that an entity experiences or has a particular emotion, sensation, or internal state in relation to something.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e933648481909873094bc89ed041 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.