Triple

T31704409
Position Surface form Disambiguated ID Type / Status
Subject EMPAR radar E809140 entity
Predicate typicalInstrumentedRange P13474 FINISHED
Object over 150 km for air targets — 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: over 150 km for air targets | Statement: [EMPAR radar, typicalInstrumentedRange, over 150 km for air targets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalInstrumentedRange
Context triple: [EMPAR radar, typicalInstrumentedRange, over 150 km for air targets]
  • A. typicalInstrumentation
    Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
  • B. typicalRangeClass
    Indicates that the related entity belongs to a class whose members typically fall within a characteristic or expected value range.
  • C. typicalRange chosen
    Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
  • D. testRange
    Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
  • E. possibleInstrumentation
    Indicates that one entity can serve as a potential instrument, tool, or means by which an action involving another entity may be carried out.
  • 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_69f348de914081909fc8edff56f34dbe completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e7aa0c8190bdc9ee4d54fc821b completed May 12, 2026, 7:05 p.m.
Created at: April 30, 2026, 11:13 p.m.