Triple
T32776408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claire Keesey |
E838218
|
entity |
| Predicate | traumatizedBy |
P168492
|
FINISHED |
| Object | bank heist |
—
|
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: bank heist | Statement: [Claire Keesey, traumatizedBy, bank heist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traumatizedBy Context triple: [Claire Keesey, traumatizedBy, bank heist]
-
A.
trauma
Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
-
B.
traumaTheme
Indicates that the relationship or context involves themes of trauma, such as psychological injury, distressing experiences, or their emotional and narrative impact.
-
C.
traumaSource
chosen
Indicates that one entity is the origin or cause of another entity’s trauma.
-
D.
traumaLevel
Indicates the degree or severity of trauma experienced or present in relation to an entity or event.
-
E.
livedAfterAssault
Indicates that the subject continued to live for some period of time following the occurrence of an assault.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.