Triple
T31611785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-N-15 Starfish |
E806645
|
entity |
| Predicate | hasWarheadOption |
P61965
|
FINISHED |
| Object | conventional torpedo 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: conventional torpedo warhead | Statement: [SS-N-15 Starfish, hasWarheadOption, conventional torpedo warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarheadOption Context triple: [SS-N-15 Starfish, hasWarheadOption, conventional torpedo warhead]
-
A.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
B.
warheadName
Indicates the specific name or designation assigned to a warhead associated with an entity or system.
-
C.
warheadTypes
chosen
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
D.
warheadNumber
Indicates the specific count or identifier assigned to a warhead associated with an entity or system.
-
E.
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.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 30, 2026, 10:37 p.m.