Triple
T15328284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALMA Operations Support Facility |
E366468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical observatory support facility |
C1469
|
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: astronomical observatory support facility Context triple: [ALMA Operations Support Facility, instanceOf, astronomical observatory support facility]
-
A.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
-
B.
observatory
chosen
An observatory is a facility equipped with specialized instruments and structures designed for systematically observing and recording natural phenomena, typically in astronomy or atmospheric science.
-
C.
astronomical support service
An astronomical support service provides specialized technical, logistical, and analytical assistance to facilitate the planning, execution, and interpretation of astronomical observations and research.
-
D.
ESA facility
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.
-
E.
astronomical observatory network
An astronomical observatory network is a coordinated system of multiple observatories that share data, resources, and observation schedules to collectively monitor and study celestial phenomena more effectively than any single facility could alone.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.