Triple

T26477600
Position Surface form Disambiguated ID Type / Status
Subject Sukhoi Su-47 E666081 entity
Predicate aerodynamicBenefit P19885 FINISHED
Object improved lift at high angles of attack 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: improved lift at high angles of attack | Statement: [Sukhoi Su-47, aerodynamicBenefit, improved lift at high angles of attack]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aerodynamicBenefit
Context triple: [Sukhoi Su-47, aerodynamicBenefit, improved lift at high angles of attack]
  • A. aerodynamicsFeature chosen
    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
    Indicates a goal or objective specifically related to aerodynamic performance, behavior, or properties in a given context.
  • C. aerodynamicsRules
    Indicates that certain aerodynamic principles or laws govern how an object moves through air or another fluid medium.
  • D. aerodynamicLoad
    Indicates the force or stress exerted on an object due to its interaction with surrounding airflow.
  • E. windResistance
    Indicates the degree to which an entity opposes or reduces the effect of wind acting upon it.
  • 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_69ee883f80dc819090e311b022b78e02 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f612ce613081908f37874b9ecfe7cc completed May 2, 2026, 3:05 p.m.
PD Predicate disambiguation batch_69f602d5c8808190a1fdbebd6f0981e8 completed May 2, 2026, 1:57 p.m.
Created at: April 27, 2026, 12:24 a.m.