Triple
T15016187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States nuclear triad |
E377964
|
entity |
| Predicate | landLegBasingMode |
P34589
|
FINISHED |
| Object | silo-based ICBMs |
—
|
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: silo-based ICBMs | Statement: [United States nuclear triad, landLegBasingMode, silo-based ICBMs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landLegBasingMode Context triple: [United States nuclear triad, landLegBasingMode, silo-based ICBMs]
-
A.
basingMode
chosen
Indicates the method or principle on which something is founded, justified, or determined.
-
B.
potentialBasing
Indicates a relationship where one entity could serve as the base, foundation, or supporting location for another, but this basing has not yet been realized or confirmed.
-
C.
standingBasis
Indicates that one entity serves as the foundational reason, justification, or basis for another entity’s standing, status, or position in a given context.
-
D.
homeGroundType
Indicates the type or category of venue that serves as an entity’s designated home ground.
-
E.
landVariant
Indicates that one landform, terrain type, or land-related entity is an alternative or variant form of another.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.