Triple
T19020611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aesacus |
E465473
|
entity |
| Predicate | causeOfBelovedsDeath |
P44824
|
FINISHED |
| Object | snakebite (indirectly) |
—
|
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: snakebite (indirectly) | Statement: [Aesacus, causeOfBelovedsDeath, snakebite (indirectly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfBelovedsDeath Context triple: [Aesacus, causeOfBelovedsDeath, snakebite (indirectly)]
-
A.
causeOfHusbandDeath
Indicates that the subject is the cause or reason for the husband’s death.
-
B.
reasonForDeath
chosen
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
motherDeath
Indicates that the mother of the referenced individual has died.
-
D.
mourningCause
Indicates that one entity is in a state of mourning specifically because of the other entity, which is the cause or reason for the grief.
-
E.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6de93408190a98dea2319f1af62 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.