Triple
T17023096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zentralblatt MATH |
E412993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematical bibliographic database |
C1031
|
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: mathematical bibliographic database Context triple: [Zentralblatt MATH, instanceOf, mathematical bibliographic database]
-
A.
bibliographic database
chosen
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.
-
B.
bibliographic database provider
A bibliographic database provider is an organization or service that collects, curates, indexes, and delivers structured metadata about publications and scholarly works for search, discovery, and analysis.
-
C.
bibliometric database
A bibliometric database is a structured collection of publication and citation data used to analyze research output, impact, and scholarly networks.
-
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 service suite
A bibliographic service suite is an integrated set of tools and services that support the creation, management, discovery, and sharing of bibliographic records and related metadata across information systems.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.