Triple
T64063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Soviet of the Soviet Union |
E1273
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former political institution |
C1003
|
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: former political institution Context triple: [Supreme Soviet of the Soviet Union, instanceOf, former political institution]
-
A.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
constitutional institution
A constitutional institution is a formally established body or office whose powers, functions, and structure are defined and limited by a constitution to uphold and operate the fundamental framework of a state.
-
C.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
-
D.
former sovereign state
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
-
E.
political organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
- F. None of above. chosen
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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.