Triple
T1004042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auschwitz death marches |
E21668
|
entity |
| Predicate | perpetrator |
P698
|
FINISHED |
| Object | SS |
E1506
|
NE 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: SS | Statement: [Auschwitz death marches, perpetrator, SS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SS Context triple: [Auschwitz death marches, perpetrator, SS]
-
A.
SS
chosen
The SS was a paramilitary organization of Nazi Germany that became one of the principal instruments of terror, repression, and mass murder, including the systematic genocide of Jews and other targeted groups during World War II.
-
B.
SS
SS is the IATA airline designator used to identify Corsair International flights in global aviation systems.
-
C.
S
S is the New York City Subway service designation used for the 42nd Street Shuttle, a short line connecting Times Square and Grand Central in Manhattan.
-
D.
S
S is the distinctive middle initial of U.S. President Harry S. Truman, famously not standing for any specific name but honoring both of his grandfathers.
-
E.
SD
SD is the abbreviated name commonly used for the SS Security Service, the intelligence and security agency of Nazi Germany’s Schutzstaffel.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4ff614081909478500ada1f5059 |
completed | March 1, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac2a1ecddc8190b954d16c6e269498 |
completed | March 7, 2026, 1:37 p.m. |
Created at: March 1, 2026, 7:41 p.m.