Triple
T25696594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Space Agency ESRIN center |
E644337
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Earth observation center |
C14251
|
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: Earth observation center Context triple: [European Space Agency ESRIN center, instanceOf, Earth observation center]
-
A.
Earth science data center
An Earth science data center is a specialized facility that archives, manages, and distributes Earth observation and geophysical data to support research, applications, and decision-making about the planet’s systems.
-
B.
satellite-based Earth observation service
A satellite-based Earth observation service collects, processes, and delivers remotely sensed data about the Earth's surface and atmosphere to support applications such as environmental monitoring, resource management, and disaster response.
-
C.
Earth observation data access tool
A software system that enables users to discover, query, and retrieve Earth observation datasets from various sensors and repositories through a unified, user-friendly interface.
-
D.
NASA center
A NASA center is a major facility or campus operated by the National Aeronautics and Space Administration that conducts research, development, testing, and mission operations in specific areas of aerospace and space exploration.
-
E.
ESA facility
chosen
An ESA facility is a specialized location, infrastructure, or installation operated or supported by the European Space Agency to conduct space-related research, development, testing, mission operations, or support 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:36 p.m.