Triple
T13464961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AURA |
E311472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomy research consortium |
C30283
|
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: astronomy research consortium Context triple: [AURA, instanceOf, astronomy research consortium]
-
A.
astronomical research collaboration
chosen
An astronomical research collaboration is a coordinated partnership of scientists, institutions, and facilities that jointly design, conduct, and analyze observations and experiments to advance understanding of the universe.
-
B.
astronomical research institute
An astronomical research institute is an organization dedicated to the systematic study of celestial objects and phenomena through observation, theory, and instrumentation development.
-
C.
research telescope
A research telescope is a precision optical or radio instrument designed to collect and analyze electromagnetic radiation from celestial objects to advance scientific understanding of the universe.
-
D.
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.
-
E.
astronomy department
An astronomy department is an academic unit within a college or university dedicated to teaching, research, and public outreach in the study of celestial objects and phenomena.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:41 p.m.