Triple
T114138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zyklon B |
E2306
|
entity |
| Predicate | associatedWithCrime |
P2830
|
FINISHED |
| Object | crimes against humanity |
—
|
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: crimes against humanity | Statement: [Zyklon B, associatedWithCrime, crimes against humanity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCrime Context triple: [Zyklon B, associatedWithCrime, crimes against humanity]
-
A.
crimeListedInArticleIII
Indicates that a particular crime is one of the offenses expressly mentioned in Article III of the relevant constitution or legal document.
-
B.
positionOnCrime
Indicates a stance, opinion, or policy position that an entity holds regarding crime or crime-related issues.
-
C.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
numberOfPeopleAccused
Indicates the count of individuals who are formally alleged to have committed a particular act or offense.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564417848190a8a8a38e97348963 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.