Triple
T37760210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henri Courpron |
E941244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation industry executive |
C10996
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: aviation industry executive Context triple: [Henri Courpron, instanceOf, aviation industry executive]
-
A.
aerospace executive
chosen
An aerospace executive is a high-level business leader responsible for guiding the strategic direction, operations, and financial performance of organizations involved in the design, manufacture, and support of aircraft, spacecraft, and related technologies.
-
B.
aviation entrepreneur
An aviation entrepreneur is an individual who identifies, develops, and commercializes innovative opportunities within the aviation industry, such as new airlines, aircraft technologies, services, or infrastructure solutions.
-
C.
aviation industry figure
An aviation industry figure is an individual who plays a significant role in the development, operation, regulation, or public perception of air transportation and related aerospace activities.
-
D.
aviation professional
An aviation professional is an individual qualified by training, certification, and experience to perform specialized roles that ensure the safe, efficient, and compliant operation of aircraft and aviation systems.
-
E.
aviation official
An aviation official is an authorized individual responsible for overseeing, regulating, and ensuring compliance with aviation laws, safety standards, and operational procedures within the air transport system.
- F. None of above.
Provenance (1 batch)
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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:19 p.m.