Triple
T29439383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | committees of the Supreme Soviet of Belarus |
E746668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legislative body subdivision |
C14322
|
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: legislative body subdivision Context triple: [committees of the Supreme Soviet of Belarus, instanceOf, legislative body subdivision]
-
A.
legislative body
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.
-
B.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
C.
standing committee of a state legislature
A standing committee of a state legislature is a permanent, specialized group of legislators that reviews, amends, and recommends action on proposed laws and issues within a specific policy area.
-
D.
legislative district system
A legislative district system is a structured method of dividing a jurisdiction into geographically or demographically defined areas, each of which elects representatives to a legislative body.
-
E.
governing body subcommittee
chosen
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:20 p.m.