Triple

T9541043
Position Surface form Disambiguated ID Type / Status
Subject Raytheon ASARS-2 derivative radar E230156 entity
Predicate operationalCondition P63497 FINISHED
Object day 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: day | Statement: [Raytheon ASARS-2 derivative radar, operationalCondition, day]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operationalCondition
Context triple: [Raytheon ASARS-2 derivative radar, operationalCondition, day]
  • A. operatingCondition chosen
    Indicates the specific state, requirements, or circumstances under which an entity functions or is intended to be used.
  • B. operationalRequirement
    Indicates that one entity specifies a condition or capability that must be met for another entity to function or operate as intended.
  • C. operationalRange
    Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
  • D. operationalNature
    Indicates the functional or practical manner in which an entity, process, or system operates or carries out its activities.
  • E. globalCondition
    Indicates that a condition applies universally or system-wide rather than being limited to a specific local context or subset.
  • 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_69ca847b1b3081908f72bc932c17cc41 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd98e695948190ab107fff38c57de7 completed April 1, 2026, 10:15 p.m.
PD Predicate disambiguation batch_69ccd58bd21881908b860e3ee469af13 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:01 p.m.