Triple
T4701588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Librarian’s Records Room |
E104284
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object |
Library of Congress records management policies
Library of Congress records management policies are the official guidelines that dictate how records are created, organized, maintained, and preserved within the Library of Congress to ensure legal compliance, accountability, and long-term access.
|
E460168
|
NE FINISHED |
How this triple was built (4 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: Library of Congress records management policies | Statement: [Librarian’s Records Room, governedBy, Library of Congress records management policies]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Library of Congress records management policies Context triple: [Librarian’s Records Room, governedBy, Library of Congress records management policies]
-
A.
Library of Congress Policy and Standards Division
The Library of Congress Policy and Standards Division is the unit within the Library of Congress responsible for developing, maintaining, and overseeing cataloging policies, standards, and classification systems used by libraries worldwide.
-
B.
Library of Congress Rule Interpretations
Library of Congress Rule Interpretations were a set of official guidelines issued by the Library of Congress to clarify and supplement AACR2 cataloging rules for librarians.
-
C.
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.
-
D.
Library of Congress Acquisitions and Bibliographic Access Directorate
The Library of Congress Acquisitions and Bibliographic Access Directorate is the division of the Library of Congress responsible for acquiring materials and creating the cataloging and bibliographic records that support access to the library’s collections.
-
E.
Archives and Records Management
Archives and Records Management is a municipal program responsible for preserving, organizing, and providing access to the official records and historical documents of the City of Portland.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Library of Congress records management policies Triple: [Librarian’s Records Room, governedBy, Library of Congress records management policies]
Generated description
Library of Congress records management policies are the official guidelines that dictate how records are created, organized, maintained, and preserved within the Library of Congress to ensure legal compliance, accountability, and long-term access.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Library of Congress records management policies Target entity description: Library of Congress records management policies are the official guidelines that dictate how records are created, organized, maintained, and preserved within the Library of Congress to ensure legal compliance, accountability, and long-term access.
-
A.
Library of Congress Policy and Standards Division
The Library of Congress Policy and Standards Division is the unit within the Library of Congress responsible for developing, maintaining, and overseeing cataloging policies, standards, and classification systems used by libraries worldwide.
-
B.
Library of Congress Rule Interpretations
Library of Congress Rule Interpretations were a set of official guidelines issued by the Library of Congress to clarify and supplement AACR2 cataloging rules for librarians.
-
C.
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.
-
D.
Library of Congress Acquisitions and Bibliographic Access Directorate
The Library of Congress Acquisitions and Bibliographic Access Directorate is the division of the Library of Congress responsible for acquiring materials and creating the cataloging and bibliographic records that support access to the library’s collections.
-
E.
Archives and Records Management
Archives and Records Management is a municipal program responsible for preserving, organizing, and providing access to the official records and historical documents of the City of Portland.
- F. None of above. chosen
Provenance (5 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd63cd447081908120ee1691009982 |
completed | March 20, 2026, 3:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be03ca24848190aa7df32472647cae |
completed | March 21, 2026, 2:34 a.m. |
| NEDg | Description generation | batch_69be04513ec081909d38f33de795402b |
completed | March 21, 2026, 2:37 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69be051027c88190a4f24ed5cb17b605 |
completed | March 21, 2026, 2:40 a.m. |
Created at: March 20, 2026, 1:17 p.m.