Triple
T12892597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Functional Requirements for Bibliographic Records |
E308404
|
entity |
| Predicate | influenced |
P9
|
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: [Functional Requirements for Bibliographic Records, influenced, Resource Description and Access]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Resource Description and Access Context triple: [Functional Requirements for Bibliographic Records, influenced, 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.
Resource Description Framework in Attributes
Resource Description Framework in Attributes (RDFa) is a W3C recommendation that extends HTML and other web documents with attributes for embedding structured, machine-readable metadata directly into human-readable content.
-
C.
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.
-
D.
REST
REST is an FTP command used to specify a restart point for resuming interrupted file transfers.
-
E.
RFC 4918
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971484aa08190a8adfafabe600903 |
completed | April 10, 2026, 9:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a55be3288190b2bc0bd197431db3 |
completed | May 3, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:40 p.m.