Triple
T25130680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Data System |
E629514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data infrastructure program |
C26346
|
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: data infrastructure program Context triple: [World Data System, instanceOf, data infrastructure program]
-
A.
data center infrastructure management platform
A data center infrastructure management platform is a centralized software system that monitors, analyzes, and optimizes the physical and virtual resources, power, cooling, and capacity of data centers to improve efficiency, reliability, and planning.
-
B.
NASA program infrastructure
NASA program infrastructure encompasses the organizational structures, facilities, technologies, processes, and support systems that enable the planning, execution, and management of NASA’s missions and research programs.
-
C.
data processing platform
chosen
A data processing platform is an integrated system that ingests, transforms, analyzes, and manages data at scale to enable efficient, reliable, and repeatable data-driven operations and insights.
-
D.
data science program
A data science program is an organized curriculum or course of study that teaches methods, tools, and theories for extracting insights and knowledge from data.
-
E.
infrastructure funding program
An infrastructure funding program is a structured initiative that allocates financial resources to plan, build, upgrade, and maintain public facilities and systems such as transportation, utilities, and community services.
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.