Triple
T34045997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ker |
E873087
|
entity |
| Predicate | typeOfDeathAssociated |
P44824
|
FINISHED |
| Object | violent death in war |
—
|
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: violent death in war | Statement: [Ker, typeOfDeathAssociated, violent death in war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDeathAssociated Context triple: [Ker, typeOfDeathAssociated, violent death in war]
-
A.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
-
B.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
C.
deathRecordType
Indicates the specific category or classification of a recorded death event within a death record system.
-
D.
reasonForDeath
chosen
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
E.
hasPartInMannerOfDeath
Indicates that an entity’s involvement in a death is characterized or qualified by a specific manner or way in which the death occurred.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0119132e848190820a688d139fbf75 |
completed | May 10, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a01188dfdec8190b7f675264a281733 |
completed | May 10, 2026, 11:45 p.m. |
Created at: May 1, 2026, 1:51 a.m.