Triple
T9541013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier Global Express |
E230155
|
entity |
| Predicate | wingDesignFeature |
P22244
|
FINISHED |
| Object | supercritical wing |
—
|
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: supercritical wing | Statement: [Bombardier Global Express, wingDesignFeature, supercritical wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wingDesignFeature Context triple: [Bombardier Global Express, wingDesignFeature, supercritical wing]
-
A.
aircraftDesignFeature
Indicates a relationship where a specific design feature is associated with, or incorporated into, an aircraft.
-
B.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
C.
aerodynamicsFeature
Indicates that one entity possesses or is characterized by a specific aerodynamic property, component, or design feature affecting airflow and motion through air.
-
D.
architectOfWing
Indicates that one entity served as the architect responsible for designing a particular wing of a building or structure.
-
E.
typeOfWing
chosen
Indicates the specific kind or category of wing that an entity possesses or is associated with.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98e695948190ab107fff38c57de7 |
completed | April 1, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ccd58bd21881908b860e3ee469af13 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:01 p.m.