Triple
T19953035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosemary |
E479605
|
entity |
| Predicate | isExecutedFor |
P137978
|
FINISHED |
| Object | murder of Big Jim |
—
|
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 of Big Jim | Statement: [Rosemary, isExecutedFor, murder of Big Jim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExecutedFor Context triple: [Rosemary, isExecutedFor, murder of Big Jim]
-
A.
executedFor
Indicates that one entity carried out an action, task, or operation on behalf of or in fulfillment of an obligation to another entity.
-
B.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
-
C.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
-
D.
isPerformedAs
Indicates that an action or role is carried out in a particular manner, style, or capacity, often differing from its original or typical form.
-
E.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65aee23488190bd92c1593fbc241c |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.