Triple
T35523453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simplified Technical English |
E1026605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace standard |
C28398
|
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: aerospace standard Context triple: [Simplified Technical English, instanceOf, aerospace standard]
-
A.
aviation standards organization
An aviation standards organization is an entity that develops, maintains, and promotes technical, safety, and operational standards to ensure interoperability, reliability, and safety across the aviation industry.
-
B.
SAE International standard
An SAE International standard is a consensus-based technical specification developed by SAE International that defines requirements, practices, or guidelines for engineering, design, testing, and performance in mobility-related industries.
-
C.
air transport industry standard
chosen
A formalized set of rules, guidelines, and technical specifications that ensure safety, interoperability, efficiency, and regulatory compliance across the global air transport industry.
-
D.
ICAO standard
An ICAO standard is an internationally agreed set of rules, specifications, and recommended practices established by the International Civil Aviation Organization to ensure the safety, regularity, and efficiency of global civil aviation.
-
E.
aerospace organization
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.