Triple
T11593491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthenian Voivodeship |
E274942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former subdivision of the Kingdom of Poland |
C30292
|
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: former subdivision of the Kingdom of Poland Context triple: [Ruthenian Voivodeship, instanceOf, former subdivision of the Kingdom of Poland]
-
A.
former territory of Poland
A former territory of Poland is a geographic area that was once under Polish sovereignty or administration but is no longer part of the modern Polish state.
-
B.
former subdivision of the Russian Empire
A former subdivision of the Russian Empire is an obsolete administrative-territorial unit that once functioned as part of the empire’s governmental structure but no longer exists in its original form.
-
C.
region of Poland
A region of Poland is a geographically and historically defined area within the country, often characterized by distinct cultural, economic, and administrative features.
-
D.
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.
-
E.
province of Prussia
A province of Prussia was a major administrative and territorial division within the Kingdom (and later Free State) of Prussia, functioning as a regional unit of government with its own local authorities under the broader Prussian state.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.