Triple
T5685690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poniatowa forced labor camp |
E125307
|
entity |
| Predicate | hasTypeOfKilling |
P61208
|
FINISHED |
| Object | mass shootings |
—
|
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: mass shootings | Statement: [Poniatowa forced labor camp, hasTypeOfKilling, mass shootings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfKilling Context triple: [Poniatowa forced labor camp, hasTypeOfKilling, mass shootings]
-
A.
typeOfKilling
chosen
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
B.
allegedToHaveKilled
Indicates that one entity is claimed or accused, but not proven, to have killed another entity.
-
C.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
D.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
E.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021be59088190a81c880957f666ab |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.