Triple
T28923951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Claythorne |
E733592
|
entity |
| Predicate | methodOfKillingPhilipLombard |
P128435
|
FINISHED |
| Object | shooting with his revolver |
—
|
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: shooting with his revolver | Statement: [Vera Claythorne, methodOfKillingPhilipLombard, shooting with his revolver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfKillingPhilipLombard Context triple: [Vera Claythorne, methodOfKillingPhilipLombard, shooting with his revolver]
-
A.
methodOfMurderScheme
chosen
Indicates the specific method or scheme by which a murder is carried out in a given situation or plan.
-
B.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
C.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
D.
notablePersonKilledThere
Indicates that a notable or famous person was killed at the referenced location.
-
E.
assassinationOrganizedBy
Indicates that an assassination was planned, directed, or coordinated by a particular agent or organization.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 8:22 a.m.