Triple

T9594033
Position Surface form Disambiguated ID Type / Status
Subject Sylver A50 VLS E231485 entity
Predicate supportsMissileType P75754 FINISHED
Object medium-range surface-to-air missile 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: medium-range surface-to-air missile | Statement: [Sylver A50 VLS, supportsMissileType, medium-range surface-to-air missile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsMissileType
Context triple: [Sylver A50 VLS, supportsMissileType, medium-range surface-to-air missile]
  • A. usesMissileSystem
    Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
  • B. supportsMissionType
    Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
  • C. missileTypeCarried chosen
    Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
  • 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. missileLaunchCapability
    Indicates that an entity has the ability or functionality to launch missiles.
  • 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_69ca8482884481908eccdfdf64d6fbf7 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a134b0c81908a568e5d2ecfbb92 completed April 1, 2026, 10:20 p.m.
PD Predicate disambiguation batch_69ccd5a359788190b24f82399489f7fe completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:07 p.m.