Triple
T5297326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vistula Land |
E119886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | province of the Russian Empire |
C5918
|
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: province of the Russian Empire Context triple: [Vistula Land, instanceOf, province of the Russian Empire]
-
A.
state institution of the Russian Empire
A state institution of the Russian Empire was an official governmental body or administrative organ responsible for implementing imperial policies, managing public affairs, and exercising authority within the empire’s centralized bureaucratic system.
-
B.
district of Russia
A district of Russia is an administrative subdivision within a federal subject that manages local governance, public services, and regional implementation of national laws for its constituent settlements.
-
C.
oblast of the Russian Empire
chosen
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 principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
E.
province of Prussia
A province of Prussia was a major administrative territorial unit within the Kingdom (and later state) of Prussia, serving as a top-level regional division for governance, law, and administration.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:53 p.m.