Triple
T37997323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beulah Annan murder case |
E947994
|
entity |
| Predicate | hasLoverVictim |
P200895
|
FINISHED |
| Object | Harry Kalstedt |
—
|
NE NERFINISHED |
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: Harry Kalstedt | Statement: [Beulah Annan murder case, hasLoverVictim, Harry Kalstedt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoverVictim Context triple: [Beulah Annan murder case, hasLoverVictim, Harry Kalstedt]
-
A.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
B.
hasVictimSpouse
Indicates that a person’s spouse is the victim in a harmful, criminal, or adverse event involving that person.
-
C.
allegedVictimOf
Indicates that one entity is claimed or reported to have been harmed, wronged, or victimized by another entity, without asserting that the claim is proven.
-
D.
perpetratorsOfLover’sMurder
Indicates that the subject is responsible for killing the lover of the specified person.
-
E.
hasMainVictim
Indicates that an event, action, or harmful situation primarily targets or affects a specific victim as its main subject.
- F. None of above. chosen
Provenance (4 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
| PDg | Predicate description generation | batch_69ffb6976f84819098a9b14946591baa |
completed | May 9, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:20 p.m.