Triple
T144433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Reserve System |
E2923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | independent government agency |
C43
|
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: independent government agency Context triple: [Federal Reserve System, instanceOf, independent government agency]
-
A.
independent regional agency
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
B.
government agency division
A government agency division is a specialized organizational unit within a larger government agency that focuses on a specific set of functions, programs, or policy areas to support the agency’s overall mission.
-
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.
United States federal government agency
chosen
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.
-
E.
science agency
A science agency is an organization, typically governmental or intergovernmental, that funds, coordinates, and oversees scientific research and development to advance knowledge and inform policy.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.