Triple
T7570849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuttle Landing Facility |
E179233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace infrastructure |
C21084
|
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 infrastructure Context triple: [Shuttle Landing Facility, instanceOf, aerospace infrastructure]
-
A.
aerospace hub
An aerospace hub is a centralized facility or region where aerospace research, manufacturing, testing, and logistics activities are concentrated to support the development and operation of aircraft and spacecraft.
-
B.
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.
-
C.
aviation infrastructure network
chosen
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
-
D.
aviation infrastructure plan
An aviation infrastructure plan is a strategic blueprint that outlines the development, expansion, maintenance, and integration of airport facilities, airspace systems, and supporting services to safely and efficiently meet current and future air transportation needs.
-
E.
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.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:51 p.m.