Triple
T17726188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazimierz Badeni |
E442466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-Hungarian politician |
C32954
|
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: Austro-Hungarian politician Context triple: [Kazimierz Badeni, instanceOf, Austro-Hungarian politician]
-
A.
Austro-Hungarian statesman
chosen
An Austro-Hungarian statesman is a high-ranking political leader or government official who played a significant role in shaping the policies, diplomacy, and administration of the Austro-Hungarian Empire.
-
B.
Austrian statesman
An Austrian statesman is a political leader or public official from Austria who plays a significant role in shaping the nation's domestic and foreign policies through governance, diplomacy, and legislative influence.
-
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.
Czechoslovak politician
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.
-
E.
Slovak nationalist politician
A Slovak nationalist politician is a political figure who advocates for the promotion, protection, and prioritization of Slovak national identity, sovereignty, culture, and interests within domestic and international politics.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:07 a.m.