Triple
T28049326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau of Archives and History |
E708777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archives administration body |
C3213
|
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: archives administration body Context triple: [Bureau of Archives and History, instanceOf, archives administration body]
-
A.
archival office
An archival office is an organizational unit responsible for systematically collecting, preserving, organizing, and providing access to records and documents of long-term administrative, legal, or historical value.
-
B.
public administration body
chosen
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
archives service
A service that systematically collects, preserves, organizes, and provides controlled access to historical records and documents in physical or digital form.
-
D.
archives
Archives are organized collections of historical documents, records, or other materials preserved for long-term reference, research, and cultural memory.
-
E.
administrative body collection
An administrative body collection is an organized grouping of official entities or agencies responsible for managing, regulating, or overseeing specific governmental or institutional functions.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:31 p.m.