Triple
T16726141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on the History of Geological Sciences |
E406468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific history organization |
C10615
|
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: scientific history organization Context triple: [Commission on the History of Geological Sciences, instanceOf, scientific history organization]
-
A.
history of science journal
A history of science journal is a scholarly periodical that publishes research articles, reviews, and essays examining the development of scientific ideas, practices, institutions, and their cultural contexts over time.
-
B.
historical library
A historical library is an institution that collects, preserves, and provides access to books, manuscripts, and other records of the past to support research, education, and cultural memory.
-
C.
history organization
chosen
A history organization is an entity dedicated to researching, preserving, interpreting, and promoting understanding of past events, cultures, and narratives through activities such as archiving, education, and public outreach.
-
D.
museum archive
A museum archive is a specialized repository where artifacts, documents, and records are systematically preserved, cataloged, and managed to support research, exhibitions, and the institution’s historical memory.
-
E.
history of science work
A history of science work is a scholarly or narrative account that examines the development of scientific ideas, practices, institutions, and figures within their historical, cultural, and social contexts.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.