Triple
T7997913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor-General of Lithuania |
E186173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial administrative position |
C16392
|
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: imperial administrative position Context triple: [Governor-General of Lithuania, instanceOf, imperial administrative position]
-
A.
colonial-style administrative position
chosen
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central power.
-
B.
public administration position
A public administration position is a role within government or public sector organizations responsible for planning, implementing, and managing policies and services that serve the public interest.
-
C.
imperial court office
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
D.
royal administrator
A royal administrator is an official responsible for managing the day-to-day governance, finances, and administrative affairs of a monarch’s realm or household.
-
E.
imperial institution
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:17 p.m.