Triple
T18590524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavendish Astrophysics Group, University of Cambridge |
E454354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysics research group |
C9288
|
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: astrophysics research group Context triple: [Cavendish Astrophysics Group, University of Cambridge, instanceOf, astrophysics research group]
-
A.
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.
-
B.
astronomical research institute
chosen
An astronomical research institute is an organization dedicated to the systematic study of celestial objects and phenomena through observation, theory, and instrumentation development.
-
C.
astrophysics program office
An astrophysics program office is an organizational unit that plans, coordinates, and manages astrophysics research missions, funding, and related scientific activities within an institution or agency.
-
D.
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.
-
E.
astronomical research collaboration
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.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.