Triple
T18589467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 112 Ocean Avenue house |
E454323
|
entity |
| Predicate | hasMurderDate |
P132700
|
FINISHED |
| Object | 1974-11-13 |
—
|
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: 1974-11-13 | Statement: [112 Ocean Avenue house, hasMurderDate, 1974-11-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMurderDate Context triple: [112 Ocean Avenue house, hasMurderDate, 1974-11-13]
-
A.
hasMurderer
Indicates that one entity is the person who committed the murder of another entity.
-
B.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
C.
hasPartInMurderOf
Indicates involvement as a contributing participant in the commission of a murder.
-
D.
hasMurderVictimCharacter
Indicates that an entity (such as a work of fiction or event) includes or involves a character who is the victim of a murder.
-
E.
assassinationDate
Indicates the date on which an assassination of the referenced entity occurred.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b4a2a0819098047ee81278bd9d |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.