Triple

T3181719
Position Surface form Disambiguated ID Type / Status
Subject Sukhoi Su-24 E66601 entity
Predicate fixedArmament P6066 FINISHED
Object 1 × GSh‑6‑23 23 mm rotary cannon 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: 1 × GSh‑6‑23 23 mm rotary cannon | Statement: [Sukhoi Su-24, fixedArmament, 1 × GSh‑6‑23 23 mm rotary cannon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fixedArmament
Context triple: [Sukhoi Su-24, fixedArmament, 1 × GSh‑6‑23 23 mm rotary cannon]
  • A. primaryArmament chosen
    Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
  • B. combatArm
    Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
  • C. secondaryArmament
    Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
  • D. armedVariants
    Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
  • E. missionEquipment
    Indicates that certain equipment is assigned to, used for, or associated with carrying out a specific mission.
  • 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_69ad8587c1bc8190a2595f2c22ee1001 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada6bd07888190b680eace8290d821 completed March 8, 2026, 4:41 p.m.
PD Predicate disambiguation batch_69ad9e02677c8190a21d93b1259b2761 completed March 8, 2026, 4:04 p.m.
Created at: March 8, 2026, 3:06 p.m.