Triple

T22722332
Position Surface form Disambiguated ID Type / Status
Subject Maneuvering Characteristics Augmentation System E561894 entity
Predicate initialDesignUsed P4831 FINISHED
Object single angle of attack sensor 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: single angle of attack sensor | Statement: [Maneuvering Characteristics Augmentation System, initialDesignUsed, single angle of attack sensor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: initialDesignUsed
Context triple: [Maneuvering Characteristics Augmentation System, initialDesignUsed, single angle of attack sensor]
  • A. designUse chosen
    Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
  • B. currentDesign
    Indicates that an entity is the presently active or most up-to-date design associated with another entity or context.
  • C. hasDesign
    Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
  • D. designedWith
    Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
  • E. hasDesignInputFrom
    Indicates that the design of one entity is based on, influenced by, or derived from input provided by 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17926ae0c8190af8493cab6b15261 completed April 29, 2026, 3:21 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:20 p.m.