Triple
T34014986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Petrovich Shuisky |
E872216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Muscovite statesman |
C61567
|
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: Muscovite statesman Context triple: [Ivan Petrovich Shuisky, instanceOf, Muscovite statesman]
-
A.
Soviet statesman
A Soviet statesman is a high-ranking political leader or government official in the Soviet Union responsible for shaping and implementing state policy, diplomacy, and ideological direction.
-
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.
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.
-
D.
Swiss statesman
A Swiss statesman is a prominent political leader from Switzerland who plays a key role in shaping national policy, representing the country domestically and internationally, and upholding its federal and democratic traditions.
-
E.
Austro-Hungarian statesman
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.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.