Triple

T15957886
Position Surface form Disambiguated ID Type / Status
Subject MARC Geographic Areas E386981 entity
Predicate relatedTo P37 FINISHED
Object MARC 21 Format for Authority Data E4784 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: MARC 21 Format for Authority Data | Statement: [MARC Geographic Areas, relatedTo, MARC 21 Format for Authority Data]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MARC 21 Format for Authority Data
Context triple: [MARC Geographic Areas, relatedTo, MARC 21 Format for Authority Data]
  • A. MARC standards chosen
    MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
  • B. 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.
  • C. MARC
    MARC is a commuter rail service in Maryland that connects Washington, D.C. with Baltimore and other regional destinations.
  • D. 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.
  • E. Functional Requirements for Authority Data
    Functional Requirements for Authority Data is an IFLA conceptual model that defines the functions, entities, and relationships needed to support authority control in library and bibliographic information 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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156fd7ce08190b5db4b486ccb6e40 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffcf16b1b881909768d18b889260da completed May 10, 2026, 12:19 a.m.
Created at: April 10, 2026, 4:53 a.m.