Triple
T10671870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Challenge Corporation |
E251507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral development agency |
C28827
|
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: bilateral development agency Context triple: [Millennium Challenge Corporation, instanceOf, bilateral development agency]
-
A.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
B.
bilateral trade association
A bilateral trade association is an organization formed between two countries to promote, facilitate, and regulate trade and economic cooperation through agreements, advocacy, and joint initiatives.
-
C.
bureau of the United States Agency for International Development
A bureau of the United States Agency for International Development is a major organizational unit within USAID responsible for planning, managing, and overseeing foreign assistance programs and policies in a specific functional or geographic area.
-
D.
regional development bank
A regional development bank is a multilateral financial institution that provides loans, grants, and technical assistance to support economic and social development within a specific geographic region.
-
E.
bureau of USAID
The bureau of USAID is a major organizational unit within the U.S. Agency for International Development responsible for planning, managing, and overseeing foreign assistance programs in a specific sector or geographic region.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:09 p.m.