Triple
T11229187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dornier Do 328 |
E265775
|
entity |
| Predicate | advancedAerodynamics |
P19885
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Dornier Do 328, advancedAerodynamics, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advancedAerodynamics Context triple: [Dornier Do 328, advancedAerodynamics, yes]
-
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.
aerodynamicsDeveloper
Indicates that an entity (typically a person or organization) is responsible for designing, developing, or improving the aerodynamic properties of another entity.
-
C.
aerodynamicGoal
Indicates a goal or objective specifically related to aerodynamic performance, behavior, or properties in a given context.
-
D.
aircraftDesignFeature
Indicates a relationship where a specific design feature is associated with, or incorporated into, an aircraft.
-
E.
avionics
Indicates that an entity is related to the electronic systems used to control, monitor, or assist the operation of aircraft or spacecraft.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e900fbcc8190a3177f8a73564433 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.