Triple
T1982828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assembly History Unit |
E43067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | records management unit |
C1500
|
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: records management unit Context triple: [Assembly History Unit, instanceOf, records management unit]
-
A.
record-keeping function
The record-keeping function is responsible for systematically capturing, organizing, maintaining, and retrieving accurate and complete information about an entity’s activities, transactions, and decisions.
-
B.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
-
C.
organizational unit of the United States Copyright Office
An organizational unit of the United States Copyright Office is a distinct internal division or office responsible for specific copyright-related functions, services, or administrative duties within the overall structure of the Copyright Office.
-
D.
clerical office
chosen
A clerical office is a workplace where administrative tasks such as record-keeping, correspondence, data entry, and document management are performed to support an organization’s operations.
-
E.
organizational unit category
An organizational unit category is a classification that groups organizational units based on shared characteristics such as function, structure, or hierarchy to support consistent management and analysis.
- F. None of above.
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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.