Triple
T34341707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward O’Kelley |
E881305
|
entity |
| Predicate | placeOfKillingOfRobertFord |
P64889
|
FINISHED |
| Object | Creede, Colorado |
—
|
NE NERFINISHED |
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: Creede, Colorado | Statement: [Edward O’Kelley, placeOfKillingOfRobertFord, Creede, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfKillingOfRobertFord Context triple: [Edward O’Kelley, placeOfKillingOfRobertFord, Creede, Colorado]
-
A.
placeOfKilling
chosen
Indicates the location where a killing event took place.
-
B.
locationOfFirstPerformanceDuringAssassination
Indicates the place where a work or performance was first presented at the time an assassination occurred.
-
C.
locatedInTheAdministrativeTerritorialEntityDuringAssassination
Indicates that an assassination took place while the subject was situated within a specified administrative territorial entity (such as a city, region, or country).
-
D.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
E.
placeOfExecution
Indicates the location where an execution or carrying out of a sentence, order, or legal punishment took place.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:58 a.m.