Triple
T31715373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyoto University Library Online Catalog |
E809440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated library system |
C1030
|
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: integrated library system Context triple: [Kyoto University Library Online Catalog, instanceOf, integrated library system]
-
A.
public library system
A public library system is an organized network of libraries, resources, services, and policies that manages the acquisition, cataloging, circulation, and access to informational and cultural materials for a community.
-
B.
online library catalog
chosen
An online library catalog is a digital system that allows users to search, browse, and access information about a library’s collection of books, media, and other resources via the internet.
-
C.
online public access system
An online public access system is a web-based interface that allows users to search, retrieve, and interact with information or resources from a publicly accessible database or catalog.
-
D.
library and information service
A library and information service is an organized system that collects, manages, and provides access to information resources and related assistance to meet the informational, educational, and recreational needs of its users.
-
E.
academic library system
An academic library system manages the acquisition, organization, discovery, circulation, and preservation of scholarly resources to support the teaching, learning, and research needs of an academic institution.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:17 p.m.