Triple
T13541617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Stone |
E323398
|
entity |
| Predicate | wantsToDo |
P88492
|
FINISHED |
| Object | murder his wife Barbara for her money |
—
|
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: murder his wife Barbara for her money | Statement: [Sam Stone, wantsToDo, murder his wife Barbara for her money]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wantsToDo Context triple: [Sam Stone, wantsToDo, murder his wife Barbara for her money]
-
A.
intendsTo
chosen
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
B.
wantedBy
Indicates that one entity is desired, sought, or wished for by another entity.
-
C.
hasToDoWith
Indicates a general, non-specific relationship or association between entities, suggesting they are related, connected, or relevant to each other in some way.
-
D.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
E.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd8ba10819098faadcc6adf251e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.