Triple
T30537291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Newton Ford |
E777181
|
entity |
| Predicate | legalStatusAfterKilling |
P121935
|
FINISHED |
| Object | convicted of murder |
—
|
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: convicted of murder | Statement: [Robert Newton Ford, legalStatusAfterKilling, convicted of murder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfterKilling Context triple: [Robert Newton Ford, legalStatusAfterKilling, convicted of murder]
-
A.
consequenceOfKilling
Indicates that one event or state occurs as a direct result of an act of killing.
-
B.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
C.
legalStatusAfterEvent
chosen
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
-
D.
legalStatusAfterEscape
Indicates the legal status or condition assigned to an individual after they have escaped from custody, confinement, or lawful control.
-
E.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 8:19 p.m.