Triple
T18785200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruskin Collection |
E459354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | natural history collection |
C31497
|
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: natural history collection Context triple: [Ruskin Collection, instanceOf, natural history collection]
-
A.
natural heritage collection
chosen
A natural heritage collection is an organized assemblage of preserved natural specimens, associated data, and documentation that represent and safeguard the biodiversity, geology, and ecosystems of a region or the planet for research, education, and conservation.
-
B.
zoological museum
A zoological museum is a public institution that collects, preserves, researches, and exhibits animal specimens and related materials to educate visitors about zoology, biodiversity, and the natural world.
-
C.
natural history reference work
A natural history reference work is a comprehensive, systematically organized resource that documents and explains the characteristics, classification, behavior, and habitats of plants, animals, and other organisms in the natural world.
-
D.
entomological collection
An entomological collection is an organized assemblage of preserved insect specimens, typically labeled and curated for scientific study, education, and reference.
-
E.
natural science resource center
A natural science resource center is a facility or program that provides access to scientific materials, equipment, information, and educational support to facilitate learning, research, and public engagement in the natural sciences.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.