Triple
T19800433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolf Carlé |
E475657
|
entity |
| Predicate | traumaticPast |
P16448
|
FINISHED |
| Object | abusive father |
—
|
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: abusive father | Statement: [Rolf Carlé, traumaticPast, abusive father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traumaticPast Context triple: [Rolf Carlé, traumaticPast, abusive father]
-
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.
hasTragicPast
chosen
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
D.
livedAfterAssault
Indicates that the subject continued to live for some period of time following the occurrence of an assault.
-
E.
periodOfAbuse
Indicates the time span during which abusive behavior occurred or was experienced.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653cb865c81909696d2b37476f62f |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.