Triple
T25743515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGM-148 Javelin |
E648281
|
entity |
| Predicate | missileContainer |
P159214
|
FINISHED |
| Object | disposable launch tube |
—
|
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: disposable launch tube | Statement: [FGM-148 Javelin, missileContainer, disposable launch tube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileContainer Context triple: [FGM-148 Javelin, missileContainer, disposable launch tube]
-
A.
missileStorage
Indicates that one entity serves as a location or facility where missiles are stored for another entity.
-
B.
missileCompartmentSupplier
Indicates that one entity supplies missile compartments to another entity.
-
C.
missileTypeCarried
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
D.
numberOfMissileTubes
Indicates the quantity of missile tubes that an entity possesses or is equipped with.
-
E.
missileCompartmentDesign
Indicates a design relationship where one entity specifies or defines the structural or functional layout of a missile compartment for another entity.
- F. None of above. chosen
Provenance (4 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1c691881908f2ab63b812d978a |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 3:47 a.m.