Triple
T35665778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA launch teams |
E1030559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace operations organization |
C5661
|
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 operations organization Context triple: [NASA launch teams, instanceOf, aerospace operations organization]
-
A.
aerospace organization
chosen
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.
-
B.
aerospace and defense organization unit
An aerospace and defense organization unit is a structured division within a larger aerospace and defense entity responsible for managing specific functions, projects, or capabilities related to the development, production, or support of aerospace and defense systems.
-
C.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
D.
aerospace finance organization
An aerospace finance organization is an entity that provides specialized financial services, capital, and risk management solutions to companies and projects within the aerospace and defense sectors.
-
E.
space operations training unit
A space operations training unit is an organizational entity responsible for preparing personnel to plan, execute, and support space missions through specialized education, simulation, and hands-on operational training.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.