Triple
T6349917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations General Assembly resolution 34/68 |
E142842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 1979 document |
C20235
|
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: 1979 document Context triple: [United Nations General Assembly resolution 34/68, instanceOf, 1979 document]
-
A.
Soviet document
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
B.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
C.
post–Cold War settlement document
A post–Cold War settlement document is a formal agreement or framework, typically involving states and international organizations, that redefines political, security, and economic arrangements in the aftermath of the Cold War’s bipolar order.
-
D.
ARPANET-era document
An ARPANET-era document is a digital or scanned artifact originating from the early internet’s ARPANET period, typically containing technical, administrative, or research information that reflects the network’s foundational development and usage.
-
E.
reference document
A reference document is an organized, authoritative source of information designed to be consulted as needed for specific facts, standards, or procedures rather than read sequentially.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:31 p.m.