Triple
T22492630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States foreign assistance architecture |
E556056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foreign assistance system |
C25915
|
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: foreign assistance system Context triple: [United States foreign assistance architecture, instanceOf, foreign assistance system]
-
A.
foreign aid legislation
Foreign aid legislation comprises the laws and policies enacted by a government to authorize, regulate, and oversee the provision of financial, technical, or humanitarian assistance to other countries or international organizations.
-
B.
military assistance program
A military assistance program is an organized initiative through which one nation or entity provides training, equipment, funding, or advisory support to strengthen the defense capabilities of another.
-
C.
foreign state supporter
A foreign state supporter is an individual, organization, or entity that provides financial, material, political, or logistical assistance to a government or regime outside their own country.
-
D.
foreign policy instrument
chosen
A foreign policy instrument is a tool or means—such as diplomacy, economic measures, military force, or cultural outreach—that a state uses to influence other international actors and achieve its external objectives.
-
E.
foreign policy legislation
Foreign policy legislation comprises the laws and statutory measures enacted by a government to define, authorize, and regulate its official relations, commitments, and actions toward other states and international organizations.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.