Triple
T37532777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan III, Duke of Brittany |
E933100
|
entity |
| Predicate | suspectedCauseOfDeath |
P27547
|
FINISHED |
| Object | poisoning |
—
|
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: poisoning | Statement: [Alan III, Duke of Brittany, suspectedCauseOfDeath, poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suspectedCauseOfDeath Context triple: [Alan III, Duke of Brittany, suspectedCauseOfDeath, poisoning]
-
A.
causeOfDeath
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.
allegedMannerOfDeath
chosen
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
D.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
E.
deathCauseUncertainty
Indicates that there is ambiguity, doubt, or lack of definitive information about the cause of death in the relationship being described.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.