Triple
T12892745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Steering Committee for Development of RDA |
E308407
|
entity |
| Predicate | usesConceptualModel |
P83760
|
FINISHED |
| Object | Functional Requirements for Bibliographic Records |
E308404
|
NE FINISHED |
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: Functional Requirements for Bibliographic Records | Statement: [Joint Steering Committee for Development of RDA, usesConceptualModel, Functional Requirements for Bibliographic Records]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Functional Requirements for Bibliographic Records Context triple: [Joint Steering Committee for Development of RDA, usesConceptualModel, Functional Requirements for Bibliographic Records]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Program for Cooperative Cataloging
The Program for Cooperative Cataloging is an international library initiative that coordinates shared cataloging standards and workflows to improve the quality and efficiency of bibliographic and authority records worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConceptualModel Context triple: [Joint Steering Committee for Development of RDA, usesConceptualModel, Functional Requirements for Bibliographic Records]
-
A.
isConceptual
Indicates that something exists as an abstract or theoretical idea rather than as a concrete, physical entity.
-
B.
hasConceptualStructure
Indicates that one entity embodies, organizes, or is characterized by a particular conceptual structure defined by another entity.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
exportsConcept
Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
-
E.
conceptualizedFor
chosen
Indicates that one entity has been conceived, designed, or mentally framed specifically for use, application, or relevance to another entity.
- F. None of above.
Provenance (4 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_69f6c0e54dc48190acf120ca5fe516ab |
completed | May 3, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.