Triple

T6172797
Position Surface form Disambiguated ID Type / Status
Subject Aeroscreen cockpit protection E137742 entity
Predicate aerodynamicRole P26461 FINISHED
Object manage airflow over cockpit 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: manage airflow over cockpit | Statement: [Aeroscreen cockpit protection, aerodynamicRole, manage airflow over cockpit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aerodynamicRole
Context triple: [Aeroscreen cockpit protection, aerodynamicRole, manage airflow over cockpit]
  • A. aerodynamicsFeature
    Indicates that one entity possesses or is characterized by a specific aerodynamic property, component, or design feature affecting airflow and motion through air.
  • B. aerodynamicGoal chosen
    Indicates a goal or objective specifically related to aerodynamic performance, behavior, or properties in a given context.
  • C. testAircraftRole
    Indicates that an aircraft is assigned or evaluated for a specific operational role or function.
  • D. usedOnAircraftRole
    Indicates that something is employed or applied in the context of a specific role or function on an aircraft.
  • E. referredAircraftRole
    Indicates that one aircraft is mentioned or designated in relation to another aircraft’s role, function, or status within a specific context or event.
  • 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_69c008a68c508190a8d78245c865960e completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d9319548190980c99f692bd4115 completed March 22, 2026, 9:22 p.m.
PD Predicate disambiguation batch_69c055f7f12881908e21c04e9b752ba4 completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:18 p.m.