Triple
T16359333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge radio source surveys |
E397269
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | radio astronomy sky survey program |
C9346
|
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: radio astronomy sky survey program Context triple: [Cambridge radio source surveys, instanceOf, radio astronomy sky survey program]
-
A.
astronomical sky survey
chosen
An astronomical sky survey is a systematic, large-scale observation program that maps and catalogs celestial objects and phenomena across wide areas of the sky using standardized instruments and methods.
-
B.
radio astronomy experiment
A radio astronomy experiment is a scientific investigation that uses radio telescopes and related instrumentation to detect, measure, and analyze radio waves from celestial sources to study the universe.
-
C.
astronomical survey
An astronomical survey is a systematic observation program that maps and catalogs celestial objects or phenomena across large regions of the sky using standardized instruments and methods.
-
D.
radio astronomy technique
A radio astronomy technique is a method or procedure used to detect, measure, and analyze radio waves from celestial sources to study the physical properties and behavior of astronomical objects and phenomena.
-
E.
astronomy research program
An astronomy research program is an organized, often long-term scientific initiative that systematically investigates celestial objects and phenomena using observational, theoretical, and computational methods to advance understanding of the universe.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.