Triple
T3250237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tea Cake |
E68158
|
entity |
| Predicate | causeOfDeathInStory |
P144
|
FINISHED |
| Object | rabies |
—
|
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: rabies | Statement: [Tea Cake, causeOfDeathInStory, rabies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathInStory Context triple: [Tea Cake, causeOfDeathInStory, rabies]
-
A.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
B.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
C.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
-
D.
deathContributedTo
Indicates that one entity played a causal or contributing role in bringing about the death of another entity.
-
E.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
- 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf40f7908190a450c3136fccb020 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41837e48190933572165be0ca38 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.