Triple
T758292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Registration Policy and Practice |
E16006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of the U.S. Copyright Office |
C5449
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: division of the U.S. Copyright Office Context triple: [Office of Registration Policy and Practice, instanceOf, division of the U.S. Copyright Office]
-
A.
division of the American Bar Association
A division of the American Bar Association is a major organizational unit within the ABA that groups members by practice area, professional role, or interest to provide specialized resources, advocacy, and networking.
-
B.
publishing division
A publishing division is an organizational unit within a company responsible for acquiring, producing, marketing, and distributing content such as books, journals, or digital media.
-
C.
record label division
A record label division is a specialized branch within a larger music company that focuses on developing, marketing, and distributing music for a particular genre, market segment, or roster of artists.
-
D.
library cataloging standard
A library cataloging standard is a formal set of rules and guidelines that ensures consistent description, organization, and access to library materials across collections and systems.
-
E.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
- F. None of above. chosen
Provenance (1 batch)
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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.