Triple
T182151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Security Agency |
E3900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former United States federal agency |
C1003
|
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: former United States federal agency Context triple: [Federal Security Agency, instanceOf, former United States federal agency]
-
A.
United States federal government agency
A United States federal government agency is an organization established by federal law or executive authority to implement, administer, and enforce specific national policies, programs, and regulations on behalf of the U.S. government.
-
B.
former political institution
chosen
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
C.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
-
D.
government agency of Washington, D.C.
A government agency of Washington, D.C. is an official public organization established by the District of Columbia government to administer local laws, provide municipal services, and implement policies within the city.
-
E.
federally owned corporation
A federally owned corporation is a government-established legal entity that operates commercial or public service activities on behalf of the federal government while retaining a distinct corporate structure.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.