Triple
T33645941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castellan of Lviv |
E861960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Lithuanian Commonwealth office |
C34360
|
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: Polish–Lithuanian Commonwealth office Context triple: [Castellan of Lviv, instanceOf, Polish–Lithuanian Commonwealth office]
-
A.
department of the Duchy of Warsaw
A department of the Duchy of Warsaw was an administrative division, similar to a province, established within the Napoleonic client state between 1807 and 1815 to organize local governance, justice, and taxation.
-
B.
institution of the Polish–Lithuanian Commonwealth
An institution of the Polish–Lithuanian Commonwealth is an organized political, legal, social, or religious body that operated within and helped structure the governance and public life of the federated Polish–Lithuanian state from 1569 to 1795.
-
C.
voivodeship of Poland
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.
-
D.
Polish noble office
chosen
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
-
E.
Polish official
A Polish official is a public servant or government representative in Poland who performs administrative, legal, or political duties within state or local institutions.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.