Triple
T17286302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | north–south axis of Berlin |
E419663
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nazi architecture project |
C39020
|
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 architecture project Context triple: [north–south axis of Berlin, instanceOf, Nazi architecture project]
-
A.
Nazi report
A Nazi report is an official document produced by Nazi authorities or affiliated organizations that records observations, decisions, policies, or activities in line with the regime’s ideological, political, or military objectives.
-
B.
Nazi propaganda work
A Nazi propaganda work is a media or artistic production intentionally created or used by the National Socialist regime to disseminate its ideology, manipulate public opinion, and legitimize its policies and actions.
-
C.
Stalinist skyscraper
A Stalinist skyscraper is a monumental high-rise building characterized by grandiose, neoclassical-inspired forms, heavy ornamentation, and a propagandistic expression of Soviet power and ideology.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
E.
Nazi economic authority
A Nazi economic authority is a state-controlled institution or official body within Nazi Germany responsible for directing, regulating, and coordinating economic activity in line with the regime’s ideological, militaristic, and autarkic goals.
- F. None of above. chosen
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.