Triple
T36906787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M51 SLBM |
E912798
|
entity |
| Predicate | nuclearWarheadModel |
P119715
|
FINISHED |
| Object | TN 75 |
—
|
NE NERFINISHED |
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: TN 75 | Statement: [M51 SLBM, nuclearWarheadModel, TN 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWarheadModel Context triple: [M51 SLBM, nuclearWarheadModel, TN 75]
-
A.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
B.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
C.
nuclearWeaponConfiguration
Indicates the specific arrangement, setup, or design characteristics associated with a nuclear weapon or nuclear weapons system.
-
D.
standardWarheadBodyFor
chosen
Indicates that one warhead body is the designated standard or default warhead body type used for a particular weapon or delivery system.
-
E.
nuclearWeaponDesign
Indicates that an entity is involved in the creation, specification, or technical configuration of a nuclear weapon.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.