Triple
T2157816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakespeare quartos |
E47931
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bibliographical corpus |
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: bibliographical corpus Context triple: [Shakespeare quartos, instanceOf, bibliographical corpus]
-
A.
documentation corpus
A documentation corpus is a structured collection of written materials, such as manuals, guides, and reference texts, compiled to provide comprehensive information and support for a specific domain, product, or system.
-
B.
bibliographic database
A bibliographic database is a structured collection of references to published literature, such as books, articles, and reports, organized to support efficient search, retrieval, and management of bibliographic information.
-
C.
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.
-
D.
bibliographic data model
A bibliographic data model is a structured framework that defines how information about published and unpublished resources (such as books, articles, and digital media) is represented, organized, and related for purposes of description, discovery, and management.
-
E.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
- F. None of above. chosen
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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:44 p.m.