Triple
T24082099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Naval Observatory |
E596530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former astronomical 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: former astronomical observatory Context triple: [Old Naval Observatory, instanceOf, former astronomical observatory]
-
A.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
-
B.
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.
-
C.
observatory director
An observatory director is the person responsible for overseeing the scientific, operational, and administrative management of an astronomical observatory, including setting research priorities, coordinating staff and resources, and ensuring effective use of observational facilities.
-
D.
astronomical observatory operator
An astronomical observatory operator is responsible for configuring, monitoring, and maintaining telescopes and related instruments to collect high-quality observational data of celestial objects and phenomena.
-
E.
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.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:43 p.m.