Triple
T2741768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volhynian Voivodeship |
E60766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of Poland |
C4704
|
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: administrative division of Poland Context triple: [Volhynian Voivodeship, instanceOf, administrative division of Poland]
-
A.
voivodeship of Poland
chosen
A voivodeship of Poland is a top-level administrative region, similar to a province, governed by both elected regional authorities and a centrally appointed governor.
-
B.
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.
-
C.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
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.
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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:56 p.m.