Triple
T32213294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope Treasury programs |
E822863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legacy observing campaign |
C60905
|
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: legacy observing campaign Context triple: [Hubble Space Telescope Treasury programs, instanceOf, legacy observing campaign]
-
A.
observing run
An observing run is a scheduled period during which a telescope or observatory is dedicated to collecting data for one or more specific astronomical projects under a defined plan and conditions.
-
B.
observatory report series
An observatory report series is a recurring, systematically organized set of publications that document, analyze, and disseminate observational data and findings from a specific observatory or network of observatories.
-
C.
observatory
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.
-
D.
observation post
An observation post is a strategically positioned location or structure used to monitor, detect, and report on activities or conditions within a specific area.
-
E.
observable
An observable is an entity whose state changes can be monitored and reacted to by other objects, typically by registering and notifying dependent observers when updates occur.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:37 a.m.