Triple
T17292913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thingstätte Heidelberg |
E419832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi-era architectural site |
C702
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Nazi-era architectural site Context triple: [Thingstätte Heidelberg, instanceOf, Nazi-era architectural site]
-
A.
Holocaust site
A Holocaust site is a location directly associated with the persecution, deportation, forced labor, or mass murder of Jews and other targeted groups by Nazi Germany and its collaborators during the Holocaust.
-
B.
Holocaust-era artifact
A Holocaust-era artifact is a physical object originating from or directly connected to the events, people, or institutions of the Holocaust, serving as tangible evidence of persecution, survival, and memory.
-
C.
cultural heritage monument in Berlin
A cultural heritage monument in Berlin is a legally protected building, site, or structure recognized for its historical, architectural, or cultural significance within the city’s heritage conservation framework.
-
D.
institution of Nazi Germany
An institution of Nazi Germany is any formal organization, governmental body, or structured system established or co-opted by the Nazi regime to implement, enforce, or propagate its totalitarian, racist, and expansionist policies between 1933 and 1945.
-
E.
World War II site
chosen
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
- F. None of above.
Provenance (1 batch)
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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.