Triple
T10127656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Schiele |
E226254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Weimar Republic politician |
C27466
|
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: Weimar Republic politician Context triple: [Martin Schiele, instanceOf, Weimar Republic politician]
-
A.
member of the Reichstag
A member of the Reichstag is an elected representative who serves in the German federal parliament, participating in national legislation, oversight of the government, and political decision-making.
-
B.
East German politician
An East German politician is a public official or political figure who was active in the governance, administration, or party structures of the former German Democratic Republic (GDR) before its reunification with West Germany in 1990.
-
C.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
-
D.
Weimar Republic organization
A Weimar Republic organization is any formal group, institution, or association that operated within Germany between 1918 and 1933, shaped by and contributing to the political, social, economic, or cultural dynamics of the Weimar era.
-
E.
Prussian statesman
A Prussian statesman is a political leader or high-ranking government official from the Kingdom of Prussia who shaped its domestic policies, diplomacy, and military strategy, often influencing broader European affairs.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:05 p.m.