Triple

T23844450
Position Surface form Disambiguated ID Type / Status
Subject Astra beyond-visual-range air-to-air missile E591080 entity
Predicate intendedWeatherConditions P1702 FINISHED
Object all weather 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: all weather | Statement: [Astra beyond-visual-range air-to-air missile, intendedWeatherConditions, all weather]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: intendedWeatherConditions
Context triple: [Astra beyond-visual-range air-to-air missile, intendedWeatherConditions, all weather]
  • A. weatherConsideration
    Indicates that certain conditions, decisions, or actions take into account or are influenced by the current or expected weather.
  • B. weatherCondition chosen
    Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
  • C. hasWeather
    Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
  • D. isWeatherProtected
    Indicates that an entity is shielded from or resistant to adverse weather conditions.
  • E. hasWeatherContext
    Indicates that something is associated with, influenced by, or described in terms of specific weather conditions or patterns.
  • 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_69e25d1de32c8190a907afe9c3d6cd6d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c88a4b948190989a261e79b996a6 completed April 29, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f1614612b481908c45d99e588882f9 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:09 p.m.