Triple

T7155177
Position Surface form Disambiguated ID Type / Status
Subject Korean cataloging rules E166789 entity
Predicate relatedTo P37 FINISHED
Object Resource Description and Access E62644 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: Resource Description and Access | Statement: [Korean cataloging rules, relatedTo, Resource Description and Access]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Resource Description and Access
Context triple: [Korean cataloging rules, relatedTo, Resource Description and Access]
  • A. Resource Description and Access chosen
    Resource Description and Access is a modern library cataloging standard that provides guidelines for describing and accessing information resources in both digital and physical formats.
  • B. Permissions API specification
    The Permissions API specification is a web standard that defines a unified way for web applications to query and manage user permission states for powerful browser features like notifications, geolocation, and camera access.
  • C. WADL
    WADL is the ICAO airport code for Lombok International Airport in Indonesia.
  • D. Yet Another Resource Negotiator
    Yet Another Resource Negotiator (YARN) is Hadoop’s cluster resource management and job scheduling framework that enables efficient execution of distributed data processing applications.
  • 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_69c68887a5cc8190bec0ea96227164f7 completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e80c747c8190a017a2b1c3e78a3f completed March 27, 2026, 8:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7adb0ea288190b7eef76de30a3a1e completed March 28, 2026, 10:30 a.m.
Created at: March 27, 2026, 2:47 p.m.