Triple
T9505706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-20 Saber |
E229262
|
entity |
| Predicate | warheadYieldCategory |
P61965
|
FINISHED |
| Object | strategic nuclear |
—
|
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: strategic nuclear | Statement: [SS-20 Saber, warheadYieldCategory, strategic nuclear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warheadYieldCategory Context triple: [SS-20 Saber, warheadYieldCategory, strategic nuclear]
-
A.
warheadEffect
Indicates the type or nature of impact, damage, or outcome produced when a warhead is used or detonated.
-
B.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
C.
warheadMass
Indicates the mass or weight of a warhead associated with an entity or system.
-
D.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
E.
explosiveYieldApprox
Indicates that one entity has an approximate explosive yield value, typically expressing the estimated magnitude of an explosion or explosive device.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9852b7e48190a8f69cbde10d2858 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.