Triple
T23286888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavendish Memorial, Bolton Abbey |
E589011
|
entity |
| Predicate | subjectDeathCause |
P144
|
FINISHED |
| Object | assassination |
—
|
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: assassination | Statement: [Cavendish Memorial, Bolton Abbey, subjectDeathCause, assassination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectDeathCause Context triple: [Cavendish Memorial, Bolton Abbey, subjectDeathCause, assassination]
-
A.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
deathDetails
Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
-
D.
deathCauseUncertainty
Indicates that there is ambiguity, doubt, or lack of definitive information about the cause of death in the relationship being described.
-
E.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19647178c8190bbca5da38472ce05 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5 p.m.