Triple
T31970207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanker |
E816290
|
entity |
| Predicate | appliesToWarheadType |
P61965
|
FINISHED |
| Object | nuclear warhead |
—
|
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: nuclear warhead | Statement: [Spanker, appliesToWarheadType, nuclear warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWarheadType Context triple: [Spanker, appliesToWarheadType, nuclear warhead]
-
A.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
B.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
C.
appliesToWeaponSystem
Indicates that something (such as a rule, configuration, or characteristic) is relevant or applicable to a particular weapon system.
-
D.
canServeAsWarheadFor
Indicates that one entity is suitable or designed to function as the warhead component for another entity, such as a missile or delivery system.
-
E.
suspectedWarheadType
Indicates that an entity is believed or assumed to have a particular type of warhead, though this has not been definitively confirmed.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 1, 2026, 12:10 a.m.