Triple
T25743514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGM-148 Javelin |
E648281
|
entity |
| Predicate | launcherReuse |
P161474
|
FINISHED |
| Object | Command Launch Unit is reusable |
—
|
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: Command Launch Unit is reusable | Statement: [FGM-148 Javelin, launcherReuse, Command Launch Unit is reusable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launcherReuse Context triple: [FGM-148 Javelin, launcherReuse, Command Launch Unit is reusable]
-
A.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
B.
launcherFeature
Indicates that one entity functions as a feature, capability, or component provided by a launcher or launching system for another entity.
-
C.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
D.
focusAfterRelaunch
Indicates that an entity regains or receives input focus after an application or process has been relaunched.
-
E.
launchAndRecovery
Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
- 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_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 22, 2026, 3:47 a.m.