Triple
T37797806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet-Chinese expedition |
E942270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint Soviet–Chinese project |
C63765
|
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: joint Soviet–Chinese project Context triple: [Soviet-Chinese expedition, instanceOf, joint Soviet–Chinese project]
-
A.
German-Soviet joint venture
A German-Soviet joint venture is a collaborative business enterprise formed between German and Soviet entities to combine resources, technology, and markets for mutual economic or industrial benefit.
-
B.
Chinese national project
A Chinese national project is a large-scale, state-led initiative undertaken by the Chinese government to advance strategic economic, technological, social, or infrastructural goals at the national level.
-
C.
Sino-Russian cooperation mechanism
The Sino-Russian cooperation mechanism is an institutionalized framework of bilateral agreements, dialogues, and joint initiatives that coordinate political, economic, security, and cultural collaboration between China and Russia.
-
D.
China–Singapore cooperative project
A China–Singapore cooperative project is a jointly planned and implemented initiative between Chinese and Singaporean entities aimed at promoting mutual economic, technological, cultural, or infrastructural development.
-
E.
Mongolian–Russian joint venture
A Mongolian–Russian joint venture is a business entity jointly owned and operated by Mongolian and Russian partners, typically established to collaborate on commercial, industrial, or resource-based projects across the two countries.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.