Triple
T224623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treblinka |
E4287
|
entity |
| Predicate | killingAgent |
P2115
|
FINISHED |
| Object | exhaust fumes |
—
|
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: exhaust fumes | Statement: [Treblinka, killingAgent, exhaust fumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killingAgent Context triple: [Treblinka, killingAgent, exhaust fumes]
-
A.
killedBy
Indicates that one entity caused the death of another entity.
-
B.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
C.
usedMethodOfKilling
chosen
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
D.
mainAttacker
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
E.
commanderAttacker
Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.