Triple
T37510697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | intake and records division |
E932208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | records management division |
C37451
|
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 division Context triple: [intake and records division, instanceOf, records management division]
-
A.
archival office
chosen
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.
archival record
An archival record is a preserved document or item, created or received in the course of activities, maintained as evidence of those activities and retained for its enduring informational, legal, or historical value.
-
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.
intergovernmental organization records
Intergovernmental organization records are documented materials produced, received, or maintained by organizations formed by sovereign states to facilitate cooperation, coordination, and decision-making on international or regional issues.
-
E.
data management body
A data management body is an organized group or authority responsible for establishing, overseeing, and enforcing policies, standards, and practices for the collection, storage, use, and protection of data within an organization or jurisdiction.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.