Triple

T27995343
Position Surface form Disambiguated ID Type / Status
Subject AK-630 E706995 entity
Predicate fireControlRadar P32605 FINISHED
Object MR-123 Vympel 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: MR-123 Vympel | Statement: [AK-630, fireControlRadar, MR-123 Vympel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fireControlRadar
Context triple: [AK-630, fireControlRadar, MR-123 Vympel]
  • A. fireControlSystem
    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. firingControl
    Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
  • D. hasFireControlSystem
    Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
  • E. radarEquipment chosen
    Indicates that one entity is radar equipment used for detecting, tracking, or measuring objects relative to another 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_69ef96b980d88190a753b2f9a978595a completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63baa8ce081909988f71080b086dc completed May 2, 2026, 6 p.m.
PD Predicate disambiguation batch_69f63710d17c819084cfe96e6df334fd completed May 2, 2026, 5:40 p.m.
Created at: April 27, 2026, 7:53 p.m.