Triple

T18798584
Position Surface form Disambiguated ID Type / Status
Subject OpenURL E459702 entity
Predicate hasStandardNumber P4626 FINISHED
Object ANSI/NISO Z39.88-2004 NE NERFINISHED

How this triple was built (3 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: ANSI/NISO Z39.88-2004 | Statement: [OpenURL, hasStandardNumber, ANSI/NISO Z39.88-2004]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ANSI/NISO Z39.88-2004
Context triple: [OpenURL, hasStandardNumber, ANSI/NISO Z39.88-2004]
  • A. Functional Requirements for Bibliographic Records
    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.
  • B. Z39.50
    Z39.50 is a client-server protocol used primarily by libraries and information services to search and retrieve bibliographic and related data from remote databases in a standardized way.
  • C. MARC standards
    MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
  • D. Joint Steering Committee for Development of RDA
    The Joint Steering Committee for Development of RDA is the international body responsible for creating and maintaining the Resource Description and Access (RDA) cataloging standard used by libraries and related institutions.
  • E. Functional Requirements for Subject Authority Data
    Functional Requirements for Subject Authority Data is an IFLA conceptual model that defines how subject authority data should be structured and used to support consistent subject access in library and information retrieval systems.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: ANSI/NISO Z39.88-2004
Target entity description: ANSI/NISO Z39.88-2004 is a widely used information standard that defines the OpenURL framework for transporting metadata and identifiers to enable context-sensitive linking in web-based information services.
  • A. Functional Requirements for Bibliographic Records
    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.
  • B. Z39.50
    Z39.50 is a client-server protocol used primarily by libraries and information services to search and retrieve bibliographic and related data from remote databases in a standardized way.
  • C. MARC standards
    MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
  • D. Joint Steering Committee for Development of RDA
    The Joint Steering Committee for Development of RDA is the international body responsible for creating and maintaining the Resource Description and Access (RDA) cataloging standard used by libraries and related institutions.
  • E. Functional Requirements for Subject Authority Data
    Functional Requirements for Subject Authority Data is an IFLA conceptual model that defines how subject authority data should be structured and used to support consistent subject access in library and information retrieval systems.
  • F. None of above. chosen

Provenance (2 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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a0215084819086bce60f95d08409 completed April 20, 2026, 3:40 a.m.
Created at: April 10, 2026, 11:53 a.m.