Triple
T33814765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV Государственная дума Российской империи |
E866641
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | законодательный орган |
C124
|
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: законодательный орган Context triple: [IV Государственная дума Российской империи, instanceOf, законодательный орган]
-
A.
organ of parliament
An organ of parliament is a formally established body or component within a parliamentary system, such as committees, chambers, or leadership offices, that performs specific legislative, oversight, or administrative functions.
-
B.
legislative body
chosen
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
C.
organ of the Assembly of the Republic
An organ of the Assembly of the Republic is an institutional body or structural component within the Assembly that performs specific legislative, administrative, or oversight functions to support its constitutional role.
-
D.
organ of the National People’s Congress
An organ of the National People’s Congress is a body established under the NPC to assist in exercising state power, performing specific legislative, supervisory, or administrative functions within China’s system of people’s congresses.
-
E.
organ of the Senate of the Republic
An organ of the Senate of the Republic is an internal institutional body or structure within the Senate that performs specific legislative, administrative, or consultative functions to support its operation and decision-making.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.