Triple
T15829683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRISMA |
E383836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian Space Agency mission |
C35866
|
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: Italian Space Agency mission Context triple: [PRISMA, instanceOf, Italian Space Agency mission]
-
A.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or strategic objectives in space exploration and utilization.
-
B.
Indian Space Research Organisation mission
An Indian Space Research Organisation mission is a coordinated spaceflight project planned, developed, and executed by ISRO to achieve specific scientific, technological, or operational objectives in space.
-
C.
ESA program
An ESA program is a coordinated set of space-related activities, missions, and projects managed by the European Space Agency to achieve specific scientific, technological, or operational objectives.
-
D.
NASA mission component
A NASA mission component is a distinct hardware, software, or operational element designed to perform a specific function that contributes to the overall objectives and success of a NASA space mission.
-
E.
European Union space program
The European Union space program is the EU’s coordinated effort to develop, operate, and regulate space-based capabilities—such as navigation, Earth observation, and secure communications—to support economic growth, security, scientific research, and strategic autonomy for its member states.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.