Triple
T13191789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Vyshnegradsky |
E314007
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Empire politician |
C8762
|
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: Russian Empire politician Context triple: [Ivan Vyshnegradsky, instanceOf, Russian Empire politician]
-
A.
Russian Empire person
chosen
A Russian Empire person is an individual who lived under the sovereignty of the Russian Empire, shaped by its political structures, social hierarchies, and cultural milieu between the early 18th and early 20th centuries.
-
B.
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.
-
C.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
D.
Russian public figure
A Russian public figure is an individual who holds a prominent, recognizable role in Russian society—such as in politics, media, culture, or business—and whose actions and opinions attract significant public and media attention.
-
E.
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.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:15 p.m.