Triple
T2681275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration No. 142-Н of the Soviet of Republics of the Supreme Soviet of the USSR |
E56578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | parliamentary declaration |
C7876
|
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: parliamentary declaration Context triple: [Declaration No. 142-Н of the Soviet of Republics of the Supreme Soviet of the USSR, instanceOf, parliamentary declaration]
-
A.
diplomatic declaration
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
B.
declaration
A declaration is a statement in a program that introduces an identifier (such as a variable, function, or type) and specifies its properties without necessarily providing its full implementation.
-
C.
parliamentary paper
chosen
A parliamentary paper is an official document produced or presented to a legislature, typically containing reports, proposals, evidence, or records used to inform and support parliamentary debate and decision-making.
-
D.
political proclamation
A political proclamation is an official public statement issued by a governing authority or political leader to declare intentions, policies, positions, or significant decisions to the populace.
-
E.
parliamentary position
A parliamentary position is a formal role or office held by an individual within a legislative body, encompassing specific duties, powers, and responsibilities in the conduct of parliamentary business.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:54 p.m.