Triple
T12271148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESA Horizon 2000 programme |
E292472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space science programme |
C31202
|
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: space science programme Context triple: [ESA Horizon 2000 programme, instanceOf, space science programme]
-
A.
space exploration programme
A space exploration programme is an organized, long-term initiative that plans, funds, and conducts missions and research activities to explore outer space and expand scientific and technological knowledge.
-
B.
spacecraft program
A spacecraft program is an organized, long-term initiative that plans, develops, launches, and operates one or more spacecraft to achieve specific scientific, commercial, or exploratory objectives.
-
C.
space technology development program
A space technology development program is an organized initiative that researches, designs, tests, and matures advanced space-related technologies to enable or enhance future space missions and capabilities.
-
D.
space programme of a country
The space programme of a country is the organized set of governmental and/or national initiatives, institutions, and activities dedicated to developing and operating space technologies, missions, and policies for scientific, commercial, military, and strategic purposes.
-
E.
space communications program
A space communications program is an organized set of missions, technologies, and operations designed to enable reliable data and signal exchange between spacecraft, satellites, and ground systems.
- F. None of above. chosen
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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.