Triple
T382754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Provisional Government |
E8715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government of Russia |
C415
|
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: government of Russia Context triple: [Russian Provisional Government, instanceOf, government of Russia]
-
A.
federal city of Russia
A federal city of Russia is a major urban locality that functions as a separate federal subject, holding the same administrative status as a region or republic and typically serving as a key political, economic, or cultural center.
-
B.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
C.
national government
chosen
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
D.
central government
The central government is the primary national authority that exercises overarching political, legislative, and administrative control over a state, coordinating and regulating functions that affect the country as a whole.
-
E.
collaborationist government
A collaborationist government is a regime established or maintained in cooperation with an occupying or foreign power, often administering local affairs while supporting the occupier’s political, military, or economic objectives.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.