Triple

T37582524
Position Surface form Disambiguated ID Type / Status
Subject Chung King E935009 entity
Predicate hasAntiAircraftArmament P118958 FINISHED
Object yes 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: yes | Statement: [Chung King, hasAntiAircraftArmament, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAntiAircraftArmament
Context triple: [Chung King, hasAntiAircraftArmament, yes]
  • A. airDefenseArmament chosen
    Indicates the weapons or systems specifically equipped on an entity for defending against aerial threats such as aircraft or missiles.
  • B. aircraftDefensiveArmament
    Indicates that an aircraft is equipped with weapons or systems specifically intended for its own defense against attacks.
  • C. aircraftArmament
    Indicates that an aircraft is equipped with a particular weapon or armament system.
  • D. armamentAsCarrier
    Indicates that one entity serves as a carrier or delivery platform for another entity used as an armament or weapon.
  • E. airDefenseSystemComponent
    Indicates that one entity is a component or subsystem of an air defense system associated with 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_69f76ece61dc8190a0ab33f8d87d0a7e completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd783fed9c81909e792702636c4f1f completed May 8, 2026, 5:44 a.m.
PD Predicate disambiguation batch_69fd7788e63c81909de22fdafcfe41c0 completed May 8, 2026, 5:41 a.m.
Created at: May 3, 2026, 4:17 p.m.