Triple
T15269545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian National Bibliographic Database |
E364984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national 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: national bibliographic database Context triple: [Australian National Bibliographic Database, instanceOf, national 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.
national library organization
A national library organization is a centralized institution responsible for collecting, preserving, and providing access to a country's published heritage and coordinating library services at the national level.
-
C.
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.
-
D.
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.
-
E.
bibliometric database
A bibliometric database is a structured collection of publication and citation data used to analyze research output, impact, and scholarly networks.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.