Triple
T5085611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muar massacre |
E114629
|
entity |
| Predicate | typeOfKilling |
P61208
|
FINISHED |
| Object | extrajudicial killing |
—
|
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: extrajudicial killing | Statement: [Muar massacre, typeOfKilling, extrajudicial killing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfKilling Context triple: [Muar massacre, typeOfKilling, extrajudicial killing]
-
A.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
B.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
C.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
D.
allegedMannerOfDeath
Indicates that the specified manner of death is claimed or reported for an entity, but not confirmed as factual.
-
E.
killedBy
Indicates that one entity caused the death of another entity.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd751db4f4819088b998d7af0e6f41 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73b2c2808190b777e2c2a8a45d3f |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:40 p.m.