Triple
T7083174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-French rivalry in India |
E165006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military rivalry |
C543
|
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: military rivalry Context triple: [Anglo-French rivalry in India, instanceOf, military rivalry]
-
A.
military confrontation
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
B.
dynastic rivalry
Dynastic rivalry is the sustained political, military, and familial competition between ruling houses or lineages for supremacy, legitimacy, and control over territories or thrones.
-
C.
geopolitical competition
Geopolitical competition is the ongoing strategic rivalry among states or blocs to secure power, influence, and advantage over territory, resources, and global governance.
-
D.
Cold War relations
Cold War relations encompass the complex political, military, economic, and ideological interactions between rival blocs—primarily the United States and the Soviet Union and their respective allies—from the late 1940s to the early 1990s, characterized by sustained tension, proxy conflicts, and nuclear deterrence without direct large-scale war between the superpowers.
-
E.
geopolitical conflict
chosen
A geopolitical conflict is a sustained struggle between nations or political entities driven by competing interests over territory, resources, ideology, or influence on the global stage.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:40 p.m.