Triple
T1025928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Vietnam |
E22138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War client state |
C857
|
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: Cold War client state Context triple: [Republic of Vietnam, instanceOf, Cold War client state]
-
A.
client state
chosen
A client state is a country that is formally independent but heavily influenced or controlled politically, economically, or militarily by a more powerful state.
-
B.
Cold War polity
A Cold War polity is a state or political entity whose institutions, policies, and international behavior are fundamentally shaped by the ideological, military, and geopolitical tensions between the U.S.-led Western bloc and the Soviet-led Eastern bloc from roughly 1947 to 1991.
-
C.
Cold War strategy
Cold War strategy is the overarching approach nations used to pursue geopolitical objectives through deterrence, proxy conflicts, ideological competition, and diplomatic maneuvering without escalating into direct large-scale war between nuclear-armed superpowers.
-
D.
historical web client
A historical web client is a software application or browser designed to access, render, and interact with web content as it appeared and functioned in specific past periods of the internet’s evolution.
-
E.
Cold War policy
Cold War policy refers to the strategic, political, military, and economic decisions and doctrines adopted by states—primarily the United States and the Soviet Union—to contain, compete with, or influence each other and their allies without escalating into direct large-scale war.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.