Triple
T9648248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RT-2 ICBM |
E233262
|
entity |
| Predicate | armsRaceContext |
P29962
|
FINISHED |
| Object | US–Soviet nuclear arms race |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: US–Soviet nuclear arms race | Statement: [RT-2 ICBM, armsRaceContext, US–Soviet nuclear arms race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armsRaceContext Context triple: [RT-2 ICBM, armsRaceContext, US–Soviet nuclear arms race]
-
A.
navalArmsRaceContext
Indicates a context in which entities are engaged in or related to competitive naval armament buildup or rivalry.
-
B.
statusDuringColdWar
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
C.
partOfColdWarContext
chosen
Indicates that something occurs within, contributes to, or is significantly shaped by the geopolitical, ideological, or military dynamics of the Cold War period.
-
D.
armsTrade
Indicates the buying, selling, or exchange of weapons or military equipment between parties.
-
E.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
- F. None of above.
Provenance (3 batches)
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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bac55b48190ab2a8f9bb83c951e |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.