Triple
T17269009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foreign Market Development Program |
E419203
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cost-share program |
C38993
|
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: cost-share program Context triple: [Foreign Market Development Program, instanceOf, cost-share program]
-
A.
reimbursement program
A reimbursement program is a structured system through which individuals or organizations are repaid for eligible expenses they have incurred, typically after submitting proof of payment and meeting predefined criteria.
-
B.
cooperative risk-sharing scheme
A cooperative risk-sharing scheme is a collaborative arrangement in which participants pool resources or contributions to collectively absorb and distribute individual losses, reducing the financial impact of adverse events on any single member.
-
C.
defense cost-sharing agreement
A defense cost-sharing agreement is a contractual arrangement in which two or more parties agree to allocate and reimburse expenses related to legal defense in connection with specified claims or proceedings.
-
D.
library cooperative program
A library cooperative program is a collaborative arrangement among multiple libraries to share resources, services, and expertise in order to expand access and reduce costs for their communities.
-
E.
concession program
A concession program is an organized initiative that offers discounted or special-rate access to goods, services, or facilities for eligible groups, such as students, seniors, or low-income individuals.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.