Triple
T18284903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W47 warhead |
E437956
|
entity |
| Predicate | associatedMissileSystem |
P23633
|
FINISHED |
| Object | Fleet Ballistic Missile system |
—
|
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: Fleet Ballistic Missile system | Statement: [W47 warhead, associatedMissileSystem, Fleet Ballistic Missile system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMissileSystem Context triple: [W47 warhead, associatedMissileSystem, Fleet Ballistic Missile system]
-
A.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
B.
associatedWithMissile
chosen
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
C.
compatibleMissile
Indicates that a missile can be correctly used with, mounted on, or launched by a given platform or launcher system.
-
D.
weaponSystemType
Indicates the specific category or kind of weapon system associated with an entity.
-
E.
numberOfMissilePods
Indicates the quantity of missile pods associated with or mounted on an entity.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500f913d48190b41a1e37ca05e8b1 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.