Triple
T14092459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Milton |
E339167
|
entity |
| Predicate | killingOfLennieMotivation |
P34163
|
FINISHED |
| Object | to spare Lennie from a worse fate |
—
|
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 spare Lennie from a worse fate | Statement: [George Milton, killingOfLennieMotivation, to spare Lennie from a worse fate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killingOfLennieMotivation Context triple: [George Milton, killingOfLennieMotivation, to spare Lennie from a worse fate]
-
A.
reasonForMurder
chosen
Indicates the motive or underlying cause that led someone to commit a murder.
-
B.
deathMotivation
Indicates a relationship where one entity’s death serves as the reason, cause, or motivating factor for another entity’s actions or state.
-
C.
killedBy
Indicates that one entity caused the death of another entity.
-
D.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
E.
threatenedToKill
Indicates that one entity has made a threat or expressed an intention to kill 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee47f0881908aea8b5231b93f2f |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.