Triple
T16565020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses V |
E402437
|
entity |
| Predicate | deathCauseHypothesis |
P67150
|
FINISHED |
| Object | smallpox |
—
|
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: smallpox | Statement: [Ramesses V, deathCauseHypothesis, smallpox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathCauseHypothesis Context triple: [Ramesses V, deathCauseHypothesis, smallpox]
-
A.
deathCauseUncertainty
chosen
Indicates that there is ambiguity, doubt, or lack of definitive information about the cause of death in the relationship being described.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
causeOfDeath
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.
deathInterpretedAs
Indicates that one entity’s death is understood, framed, or interpreted in a particular way by another entity or within a given context.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e357711ea481909468147375051bb4 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.