Triple

T4425804
Position Surface form Disambiguated ID Type / Status
Subject RDA E95205 entity
Predicate basedOn P98 FINISHED
Object FRBR E308404 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: FRBR | Statement: [RDA, basedOn, FRBR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FRBR
Context triple: [RDA, basedOn, FRBR]
  • A. BIBFRAME
    BIBFRAME (Bibliographic Framework) is a linked data model and standard developed by the Library of Congress to replace MARC for describing and sharing bibliographic information on the web.
  • B. Functional Requirements for Bibliographic Records chosen
    Functional Requirements for Bibliographic Records (FRBR) is a conceptual model developed by the International Federation of Library Associations to define user-focused tasks and relationships for bibliographic records in library catalogs.
  • C. MARC
    MARC is a regional planning and coordination agency serving the Kansas City metropolitan area, focusing on transportation, emergency services, environmental planning, and community development.
  • D. MARC
    MARC is a commuter rail service in Maryland that connects Washington, D.C. with Baltimore and other regional destinations.
  • E. Dublin Core
    Dublin Core is a widely used standard for describing digital resources through a simple, generic set of metadata elements to support discovery and interoperability across systems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69b3453c2a0c8190926b574c90766db9 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b3554e40ec8190982acc0948da2f42 completed March 13, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69b5f633a69c8190b062c2a78b0f8319 completed March 14, 2026, 11:58 p.m.
Created at: March 12, 2026, 11:30 p.m.