Triple
T29250882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary MacGregor |
E741562
|
entity |
| Predicate | causeOfDeathInNarrative |
P144
|
FINISHED |
| Object | clan violence |
—
|
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: clan violence | Statement: [Mary MacGregor, causeOfDeathInNarrative, clan violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathInNarrative Context triple: [Mary MacGregor, causeOfDeathInNarrative, clan violence]
-
A.
deathNarrativeFunction
Indicates that a character’s death serves a specific narrative role or function within the story’s structure or themes.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
D.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
E.
hasCauseNarrative
Indicates that one entity provides a narrative or explanatory account of the cause or causal background of another entity or event.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 28, 2026, 12:34 p.m.