Triple
T18695671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Observatory of the Hôtel de Cluny |
E457108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical observatory |
C1469
|
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: historical observatory Context triple: [Observatory of the Hôtel de Cluny, instanceOf, historical observatory]
-
A.
observatory
chosen
An observatory is a facility equipped with specialized instruments and structures designed for systematically observing and recording natural phenomena, typically in astronomy or atmospheric science.
-
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.
historical scientific instrument
A historical scientific instrument is a physical device, typically from a past era, designed and used to observe, measure, or experiment in the natural sciences, reflecting the technological and conceptual understanding of its time.
-
D.
observatory instrument collection
A collection of observatory instruments represents an organized set of scientific devices and sensors used together at an observatory to observe, measure, and record astronomical or atmospheric phenomena.
-
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.
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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.