Triple
T3632814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden Caulfield |
E76995
|
entity |
| Predicate | traumaticEvent |
P41242
|
FINISHED |
| Object | death of his brother Allie |
—
|
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: death of his brother Allie | Statement: [Holden Caulfield, traumaticEvent, death of his brother Allie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traumaticEvent Context triple: [Holden Caulfield, traumaticEvent, death of his brother Allie]
-
A.
trauma
chosen
Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
-
B.
traumaLevel
Indicates the degree or severity of trauma experienced or present in relation to an entity or event.
-
C.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
D.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
E.
emergencyEvent
Indicates that an urgent, unexpected, and potentially harmful situation or incident has occurred requiring immediate attention or response.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30457608190840fb5b33f9965c4 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.