Triple
T2065907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian National Council for the Study of the Securitate Archives |
E45899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | archives authority |
C835
|
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 authority Context triple: [Romanian National Council for the Study of the Securitate Archives, instanceOf, archives authority]
-
A.
archives
chosen
Archives are organized collections of historical documents, records, or other materials preserved for long-term reference, research, and cultural memory.
-
B.
authority control file
An authority control file is a structured database that standardizes names, subjects, and titles to ensure consistent identification and retrieval of entities across bibliographic and information systems.
-
C.
bibliographic authority data set
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
-
D.
acquisition authority
Acquisition authority is the legally granted power or permission for an individual or organization to obtain, purchase, or otherwise secure goods, services, or assets on behalf of an entity.
-
E.
combined authority
A combined authority is a legal entity formed by two or more local government areas that collaborate to exercise shared strategic powers and responsibilities, typically over transport, economic development, and regional planning.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:40 p.m.