Triple

T25218868
Position Surface form Disambiguated ID Type / Status
Subject Buk-M1 E631904 entity
Predicate fireControlRadarDesignation P18627 FINISHED
Object 9S470M1 NE NERFINISHED

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: 9S470M1 | Statement: [Buk-M1, fireControlRadarDesignation, 9S470M1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fireControlRadarDesignation
Context triple: [Buk-M1, fireControlRadarDesignation, 9S470M1]
  • A. fireControlSystem chosen
    Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
  • B. fireControlFeature
    Indicates a relationship where an entity possesses or is associated with a capability or mechanism for directing, managing, or controlling the use of fire or weapon fire.
  • C. radarEquipment
    Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another entity.
  • D. firingControl
    Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
  • E. radarSignatureGoal
    Indicates the intended or target characteristics of an object's radar signature, typically used as a design or performance objective for how it should appear on radar.
  • 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_69e75a8d1aa48190a4320acd3654762c completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47b907f6081908c6c0e33f4cae736 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f44d849e7c81909945438f40e35362 completed May 1, 2026, 6:51 a.m.
Created at: April 21, 2026, 12:59 p.m.