Triple
T24729677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mk 41 VLS |
E618249
|
entity |
| Predicate | supportsMissile |
P116373
|
FINISHED |
| Object | RIM-66 Standard Missile 2 |
—
|
NE NERFINISHED |
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: RIM-66 Standard Missile 2 | Statement: [Mk 41 VLS, supportsMissile, RIM-66 Standard Missile 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMissile Context triple: [Mk 41 VLS, supportsMissile, RIM-66 Standard Missile 2]
-
A.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
B.
compatibleMissile
chosen
Indicates that a missile can be correctly used with, mounted on, or launched by a given platform or launcher system.
-
C.
supportsWeapon
Indicates that one entity is capable of accommodating, using, or being compatible with a specified weapon.
-
D.
associatedWithMissile
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
E.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:02 a.m.