Triple
T1001762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independent Task Force Program |
E21618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Council on Foreign Relations program |
C4631
|
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: Council on Foreign Relations program Context triple: [Independent Task Force Program, instanceOf, Council on Foreign Relations program]
-
A.
United Nations program
A United Nations program is an organized, mandate-driven initiative established by the UN to address specific global issues—such as development, health, human rights, or the environment—through coordinated policies, projects, and partnerships among member states and stakeholders.
-
B.
fellowship program
A fellowship program is a structured, time-bound opportunity that provides individuals with financial support, mentorship, and professional development to advance their skills, research, or leadership in a specific field.
-
C.
domestic policy program
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
-
D.
foreign policy agenda
A foreign policy agenda is a strategic set of priorities, goals, and planned actions that guide a state's interactions and relationships with other countries and international actors.
-
E.
international programme
An international programme is a coordinated set of activities, courses, or initiatives designed and delivered across multiple countries or cultures to achieve shared educational, developmental, or strategic objectives.
- F. None of above. chosen
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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.