Triple
T303647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidium of the Supreme Soviet of the USSR |
E6250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state organ |
C172
|
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: state organ Context triple: [Presidium of the Supreme Soviet of the USSR, instanceOf, state organ]
-
A.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
B.
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.
-
C.
organ of the Holy See
An organ of the Holy See is an official body, institution, or office that acts on behalf of the Holy See to exercise its spiritual, administrative, diplomatic, or judicial functions within the Catholic Church and in relations with states and international organizations.
-
D.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
E.
bi-state agency
A bi-state agency is a governmental or quasi-governmental organization jointly created and governed by two neighboring states to manage shared resources, infrastructure, or regulatory responsibilities across their common jurisdiction.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.