Triple
T26324365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 National Archives documents removal controversy |
E662207
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | records management controversy |
C18730
|
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 controversy Context triple: [2003 National Archives documents removal controversy, instanceOf, records management controversy]
-
A.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
-
B.
FOIA ombudsman
A FOIA ombudsman is a neutral official who assists requesters and government agencies in resolving disputes and improving compliance with the Freedom of Information Act.
-
C.
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.
-
D.
archival release
An archival release is a published collection of previously unreleased, rare, or historically significant recordings or materials drawn from an organization’s or artist’s archives.
-
E.
controversy
chosen
Controversy is a state of public disagreement or heated debate arising from conflicting opinions, values, or interpretations about a particular issue, event, or decision.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:30 p.m.