Triple

T4455369
Position Surface form Disambiguated ID Type / Status
Subject Boeing T-7A Red Hawk E97707 entity
Predicate designedForCompatibilityWith P9494 FINISHED
Object F-22 Raptor avionics concepts 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: F-22 Raptor avionics concepts | Statement: [Boeing T-7A Red Hawk, designedForCompatibilityWith, F-22 Raptor avionics concepts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForCompatibilityWith
Context triple: [Boeing T-7A Red Hawk, designedForCompatibilityWith, F-22 Raptor avionics concepts]
  • A. isGenerallyCompatibleWith
    Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
  • B. requiresCompatibilityWith
    Indicates that one entity can only function correctly or be used if it is compatible with another specified entity.
  • C. backwardCompatibleWith
    Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
  • D. isDesignedFor chosen
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
  • E. backwardCompatibility
    Indicates that one entity remains functional or compatible when used with an earlier version or older form of 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_69b3454777808190b78aa9047ba1f018 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355f79ca481909338dda9f4f7171f completed March 13, 2026, 12:10 a.m.
PD Predicate disambiguation batch_69b34f649df081909d3cc2f6a1b8f282 completed March 12, 2026, 11:42 p.m.
Created at: March 12, 2026, 11:33 p.m.