Triple

T3738423
Position Surface form Disambiguated ID Type / Status
Subject RBS 70 E79641 entity
Predicate countermeasureResistance P43585 FINISHED
Object high resistance to infrared countermeasures 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: high resistance to infrared countermeasures | Statement: [RBS 70, countermeasureResistance, high resistance to infrared countermeasures]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: countermeasureResistance
Context triple: [RBS 70, countermeasureResistance, high resistance to infrared countermeasures]
  • A. countermeasuresFaced
    Indicates that one entity has encountered or had to deal with countermeasures implemented by another entity.
  • B. controlMeasure
    Indicates a relationship where one entity implements or applies a method, action, or mechanism to regulate, mitigate, or manage a risk, process, or condition associated with another entity.
  • C. counterattackBy
    Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
  • D. typeOfResistance chosen
    Indicates the kind or category of resistance that characterizes how an entity opposes, impedes, or withstands another entity or influence.
  • E. protectionMeasures
    Indicates actions or safeguards implemented to prevent harm, damage, or risk to someone or something.
  • 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_69ad8b115610819095b02007da5ca3cb completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb3e9248819098d481fe29e1c628 completed March 8, 2026, 7:17 p.m.
PD Predicate disambiguation batch_69adc048f28c819092bed16a95a3cac1 completed March 8, 2026, 6:30 p.m.
Created at: March 8, 2026, 3:34 p.m.