Triple
T36019783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyula Andrássy |
E1041949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hungarian statesman |
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: Hungarian statesman Context triple: [Gyula Andrássy, instanceOf, Hungarian statesman]
-
A.
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.
-
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.
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.
-
D.
Romanian statesman
A Romanian statesman is a prominent political leader from Romania who plays a key role in shaping national policy, governance, and the country’s direction in domestic and international affairs.
-
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.
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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.