Triple
T28948001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peroz I |
E730930
|
entity |
| Predicate | notableConsequenceOfDeath |
P27814
|
FINISHED |
| Object | increased Hephthalite influence over the Sasanian Empire |
—
|
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: increased Hephthalite influence over the Sasanian Empire | Statement: [Peroz I, notableConsequenceOfDeath, increased Hephthalite influence over the Sasanian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableConsequenceOfDeath Context triple: [Peroz I, notableConsequenceOfDeath, increased Hephthalite influence over the Sasanian Empire]
-
A.
namedAfterCauseOfDeath
Indicates that an entity is named after the cause of death of a person or organism.
-
B.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
C.
consequenceOfKilling
Indicates that one event or state occurs as a direct result of an act of killing.
-
D.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
E.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01c303af6081909c229b2c8e91c680 |
completed | May 11, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a01c28ebf54819094318c447d8c7943 |
completed | May 11, 2026, 11:50 a.m. |
Created at: April 28, 2026, 8:41 a.m.