Triple
T32558763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rictus Erectus |
E832161
|
entity |
| Predicate | deathCauseInWork |
P144
|
FINISHED |
| Object | killed during final battle at the War Rig |
—
|
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: killed during final battle at the War Rig | Statement: [Rictus Erectus, deathCauseInWork, killed during final battle at the War Rig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathCauseInWork Context triple: [Rictus Erectus, deathCauseInWork, killed during final battle at the War Rig]
-
A.
killedInWork
Indicates that an entity died as a result of circumstances or actions occurring in the course of their work or professional duties.
-
B.
causeOfDeath
chosen
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
C.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
D.
deathDetails
Indicates the specific circumstances, causes, and contextual information associated with an entity’s death.
-
E.
constructionAccidentFatalities
Indicates that a construction-related accident resulted in one or more fatalities.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:03 a.m.