Triple
T30694494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Page Corps |
E781419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Russian institution |
C10889
|
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 Russian institution Context triple: [Page Corps, instanceOf, Imperial Russian institution]
-
A.
state institution of the Russian Empire
chosen
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.
Prussian state institution
A Prussian state institution is a formal governmental body or organization established by the Kingdom of Prussia to administer public affairs, implement state policies, and maintain social order within its territories.
-
C.
oblast of the Russian Empire
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 state
The Russian state is a centralized political entity that exercises sovereign authority over the territory and population of Russia through its institutions of governance, law, security, and administration.
-
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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.