Triple

T12202988
Position Surface form Disambiguated ID Type / Status
Subject David’s Sling E290761 entity
Predicate hasLauncherConfiguration P13644 FINISHED
Object multiple canisterized interceptors per launcher 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: multiple canisterized interceptors per launcher | Statement: [David’s Sling, hasLauncherConfiguration, multiple canisterized interceptors per launcher]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLauncherConfiguration
Context triple: [David’s Sling, hasLauncherConfiguration, multiple canisterized interceptors per launcher]
  • A. hasLaunchContext
    Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
  • B. hasConfiguration chosen
    Indicates that an entity is associated with or defined by a particular configuration or setup.
  • C. hasConfigurationFile
    Indicates that an entity is associated with or defined by a specific configuration file.
  • D. hasLaunchedFor
    Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
  • E. hasLaunchHistoryEvent
    Indicates that there exists a recorded event in the launch history associated with the given 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_69d6ab65923081909acfc61b7a612233 completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d938cd2edc8190b1971349dbc0dee0 completed April 10, 2026, 5:52 p.m.
PD Predicate disambiguation batch_69d91c38321c819080d500d0d64a04f6 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:51 p.m.