Triple
T13159926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cowra breakout |
E312697
|
entity |
| Predicate | causeOfDeathForManyPrisoners |
P44824
|
FINISHED |
| Object | suicide or being shot while escaping |
—
|
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: suicide or being shot while escaping | Statement: [Cowra breakout, causeOfDeathForManyPrisoners, suicide or being shot while escaping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfDeathForManyPrisoners Context triple: [Cowra breakout, causeOfDeathForManyPrisoners, suicide or being shot while escaping]
-
A.
causeOfSufferingAtExecution
Indicates that something is the reason or source of suffering experienced by an entity at the time of its execution.
-
B.
diedInCustodyOf
Indicates that an individual died while under the control, supervision, or physical custody of a specified authority or entity.
-
C.
estimatedPrisonersKilled
Indicates the estimated number of prisoners who were killed in a given context or event.
-
D.
numberSentencedToDeath
Indicates the number of individuals who have been formally sentenced to receive the death penalty.
-
E.
reasonForDeath
chosen
Indicates the cause, circumstance, or condition that led to an entity’s death.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.