Triple
T22307910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Childers |
E551432
|
entity |
| Predicate | motiveForKillingDoyleHargraves |
P34163
|
FINISHED |
| Object | to protect Frank and Linda |
—
|
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: to protect Frank and Linda | Statement: [Karl Childers, motiveForKillingDoyleHargraves, to protect Frank and Linda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motiveForKillingDoyleHargraves Context triple: [Karl Childers, motiveForKillingDoyleHargraves, to protect Frank and Linda]
-
A.
reasonForMurder
chosen
Indicates the motive or underlying cause that led someone to commit a murder.
-
B.
hasMotiveOfCriminals
Indicates that the specified motive is attributed to or associated with the criminals in question.
-
C.
reasonForKillingDidyme
Indicates that one entity is the cause, motive, or justification for another entity killing Didyme.
-
D.
methodOfMurderScheme
Indicates the specific method or scheme by which a murder is carried out in a given situation or plan.
-
E.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1574bccb08190a6236dd14cf0fc5b |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.