Triple
T26033962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAIR |
E647503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal regulatory program |
C420
|
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: United States federal regulatory program Context triple: [CAIR, instanceOf, United States federal regulatory program]
-
A.
United States federal government program
chosen
A United States federal government program is an organized set of activities, services, or regulations funded and administered by federal agencies to implement national policies and address public needs.
-
B.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
C.
government regulatory program
A government regulatory program is an organized set of rules, procedures, and enforcement mechanisms established by a public authority to oversee, control, or guide specific activities or sectors in order to achieve defined policy objectives and protect the public interest.
-
D.
federal government program
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
E.
U.S. federal planning instrument
A U.S. federal planning instrument is an official document or tool used by federal agencies to set goals, allocate resources, and coordinate actions over a defined time horizon in support of national policies and programs.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.