Triple
T847902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ei Compendex |
E18317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indexing and abstracting service |
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: indexing and abstracting service Context triple: [Ei Compendex, instanceOf, indexing and abstracting service]
-
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 identifier
A bibliographic identifier is a standardized code or string that uniquely distinguishes a specific published or unpublished bibliographic resource within catalogs, databases, or information systems.
-
C.
legal indexing system
A legal indexing system is a structured framework that organizes, categorizes, and cross-references legal documents, statutes, cases, and related materials to enable efficient search and retrieval.
-
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.
library cataloging tool
A library cataloging tool is a system that helps librarians and users organize, classify, and retrieve library materials efficiently through standardized metadata and search functions.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:38 p.m.