Triple
T38137904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Security Cooperation |
E952399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States government program category |
C45428
|
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 government program category Context triple: [Security Cooperation, instanceOf, United States government program category]
-
A.
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.
-
B.
United States federal government program
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.
-
C.
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.
-
D.
government program category
chosen
A government program category is a classification that groups public initiatives, services, or funding efforts based on their shared policy goals, target populations, or functional areas.
-
E.
United States Department of Agriculture program category
A United States Department of Agriculture program category is a classification grouping USDA initiatives, services, and funding programs that share common objectives, target populations, or policy areas within the agency’s mission.
- 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_69f76f09a7148190a4b91c0bacdc127a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.