Triple
T36204859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatican Observatory Research Group in Tucson |
E1047369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical research institution |
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: astronomical research institution Context triple: [Vatican Observatory Research Group in Tucson, instanceOf, astronomical research institution]
-
A.
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.
-
B.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
-
C.
astronomical research fund
An astronomical research fund is a dedicated pool of financial resources used to support scientific investigations, observations, and related activities in the field of astronomy and astrophysics.
-
D.
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.
-
E.
astronomy research group
An astronomy research group is a collaborative team of scientists, students, and technical staff who design and conduct observational, theoretical, and computational studies to investigate celestial objects and phenomena in 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.