Triple
T31733453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT Haystack Observatory |
E809922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geoscience research facility |
C20441
|
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: geoscience research facility Context triple: [MIT Haystack Observatory, instanceOf, geoscience research facility]
-
A.
earth science research centre
chosen
A facility dedicated to conducting scientific investigations and analyses of Earth's systems, including its atmosphere, oceans, landforms, and ecosystems, to advance understanding of environmental processes and changes.
-
B.
United States Geological Survey facility
A United States Geological Survey facility is a government-operated site where scientific research, monitoring, and data collection on the nation’s natural resources, hazards, and landscapes are conducted and managed.
-
C.
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.
-
D.
U.S. Geological Survey facility
A U.S. Geological Survey facility is a government-operated site where scientists conduct research, monitoring, and data analysis on the nation’s natural resources, hazards, and landscapes to support informed decision-making and public safety.
-
E.
geoscience database
A geoscience database is a structured repository that stores, organizes, and enables retrieval and analysis of spatial, geological, geophysical, and geochemical data about the Earth.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:22 p.m.