Triple
T13397083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold Berchtold |
E319725
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Austro-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: Austro-Hungarian statesman Context triple: [Leopold Berchtold, instanceOf, Austro-Hungarian statesman]
-
A.
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.
-
B.
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.
-
C.
chancellor of Austria
The chancellor of Austria is the head of government who leads the federal cabinet, directs national policy, and represents the executive branch in the Republic of Austria.
-
D.
Montenegrin statesman
A Montenegrin statesman is a political leader or public official from Montenegro who plays a significant role in shaping the country's domestic and foreign policies through governance, diplomacy, and public service.
-
E.
Austrian civil servant
An Austrian civil servant is a government employee in Austria responsible for implementing public policies, administering state functions, and providing services to citizens in accordance with national laws and regulations.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:34 p.m.