Triple
T15429856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO Users Committee |
E369608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical advisory committee |
C36145
|
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 advisory committee Context triple: [ESO Users Committee, instanceOf, astronomical advisory committee]
-
A.
American Astronomical Society committee
An American Astronomical Society committee is a formally organized group within the AAS tasked with addressing specific scientific, policy, educational, or organizational issues in support of the society’s mission to advance astronomy and related sciences.
-
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 support service
An astronomical support service provides specialized technical, logistical, and analytical assistance to facilitate the planning, execution, and interpretation of astronomical observations and research.
-
D.
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.
-
E.
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.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
Created at: April 10, 2026, 3:21 a.m.