Triple
T3462676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewis Clive |
E73061
|
entity |
| Predicate | hasMannerOfDeath |
P48923
|
FINISHED |
| Object | death in battle |
—
|
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: death in battle | Statement: [Lewis Clive, hasMannerOfDeath, death in battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMannerOfDeath Context triple: [Lewis Clive, hasMannerOfDeath, death in battle]
-
A.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
-
B.
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.
-
C.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
D.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
-
E.
traditionalMannerOfDeath
Indicates that an entity died in a way that follows or reflects a culturally recognized or customary method of death.
- F. None of above. chosen
Provenance (4 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.