Triple
T10258709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW (Gesamtkatalog der Wiegendrucke) |
E240539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research infrastructure for book history |
C9580
|
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: research infrastructure for book history Context triple: [GW (Gesamtkatalog der Wiegendrucke), instanceOf, research infrastructure for book history]
-
A.
textual scholarship project
A textual scholarship project is a systematic, research-driven endeavor focused on discovering, analyzing, editing, and interpreting texts (often historical or literary) to establish reliable versions and deepen understanding of their production, transmission, and reception.
-
B.
bibliographical corpus
chosen
A bibliographical corpus is a structured collection of bibliographic records or references, typically compiled for systematic analysis, cataloging, or research on published works.
-
C.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
D.
research library
A research library is a specialized institution that collects, organizes, preserves, and provides access to scholarly resources and reference services to support advanced study and original research.
-
E.
bibliographic project
A bibliographic project is an organized effort to collect, describe, and manage references to published or unpublished works around a specific topic, author, or field.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:31 a.m.