Triple
T4304637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolf Beran |
E99924
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Czech politician |
C10934
|
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: Czech politician Context triple: [Rudolf Beran, instanceOf, Czech politician]
-
A.
Czechoslovak politician
chosen
A Czechoslovak politician is a public figure who held governmental or party office in the former state of Czechoslovakia, influencing its domestic and foreign policies before its dissolution in 1993.
-
B.
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.
-
C.
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.
-
D.
Belarusian politician
A Belarusian politician is an individual actively involved in the governance, political decision-making, or public administration of Belarus, typically holding or seeking a public office within its political system.
-
E.
President of Czechoslovakia
The President of Czechoslovakia was the head of state of Czechoslovakia, responsible for representing the country, appointing governments, and performing key constitutional and ceremonial duties within its political system.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:09 p.m.