Triple

T16425856
Position Surface form Disambiguated ID Type / Status
Subject FIM-92 Stinger E398940 entity
Predicate seekerFeatures P17581 FINISHED
Object infrared and ultraviolet discrimination 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: infrared and ultraviolet discrimination | Statement: [FIM-92 Stinger, seekerFeatures, infrared and ultraviolet discrimination]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seekerFeatures
Context triple: [FIM-92 Stinger, seekerFeatures, infrared and ultraviolet discrimination]
  • A. seekerCapability chosen
    Indicates that an entity has the ability or function to detect, track, or locate a target or object.
  • B. seekerType
    Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
  • C. featuresIn
    Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
  • D. searchFeature
    Indicates that an entity provides or supports functionality for searching or querying information or items.
  • E. featuresSuit
    Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328faa7448190a2606f1b37ea0a3d completed April 18, 2026, 6:47 a.m.
PD Predicate disambiguation batch_69e22701d2288190bf8676050758f172 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:09 a.m.