Triple
T35791088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force archives |
E1034692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | records management institution |
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 institution Context triple: [Air Force archives, instanceOf, records management institution]
-
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 research facility
An archival research facility is a specialized institution that preserves, organizes, and provides controlled access to historical documents and records for scholarly and public research.
-
C.
archival institution network
An archival institution network is a coordinated system of archives and related organizations that collaborate to preserve, manage, and provide access to documentary heritage across multiple institutions.
-
D.
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.
-
E.
information management organization
An information management organization is an entity responsible for systematically collecting, organizing, securing, maintaining, and providing access to information resources to support decision-making, operations, and compliance within or across institutions.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.