Triple
T6119730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRBNF11864601 |
E136451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BNF authority record |
C1037
|
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: BNF authority record Context triple: [FRBNF11864601, instanceOf, BNF authority record]
-
A.
bibliographic authority data set
chosen
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.
-
B.
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.
-
C.
bibliographic data format
A bibliographic data format is a structured specification for representing, organizing, and exchanging information about published and unpublished resources such as books, articles, and other media.
-
D.
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.
-
E.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:14 p.m.