Triple
T31397198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–Soviet cultural exchange agreement |
E800894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural exchange agreement |
C44101
|
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: cultural exchange agreement Context triple: [United States–Soviet cultural exchange agreement, instanceOf, cultural exchange agreement]
-
A.
bilateral diplomatic agreement
chosen
A bilateral diplomatic agreement is a formal, negotiated arrangement between two sovereign states that defines mutual rights, obligations, and cooperative actions in specific areas of shared interest.
-
B.
bilateral economic agreement
A bilateral economic agreement is a formal arrangement between two countries that establishes rules and commitments to govern their economic relations, such as trade, investment, and financial cooperation.
-
C.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
D.
cultural exchange network
A cultural exchange network is a structured system that connects individuals or groups from different cultural backgrounds to share traditions, knowledge, and experiences, fostering mutual understanding and collaboration.
-
E.
international agreement package
An international agreement package is a bundled set of formally negotiated documents, terms, and supporting materials that collectively define and govern a cross-border accord between participating entities or nations.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.