Triple
T6167158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Consolidation Loan |
E137596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | student loan consolidation product |
C9124
|
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: student loan consolidation product Context triple: [Direct Consolidation Loan, instanceOf, student loan consolidation product]
-
A.
student loan servicer
A student loan servicer is an organization that manages student loan accounts on behalf of lenders or the government, handling billing, payment processing, customer support, and repayment options for borrowers.
-
B.
loan program
chosen
A loan program is a structured financial offering that provides borrowers with funds under defined terms, such as interest rates, repayment schedules, and eligibility criteria, to support specific purposes like education, housing, or business development.
-
C.
529 college savings plan
A 529 college savings plan is a tax-advantaged investment account designed to help families save for qualified education expenses such as tuition, fees, and room and board.
-
D.
moneylender
A moneylender is a person or entity that provides loans, typically at interest, often operating outside formal banking systems and sometimes serving borrowers who lack access to traditional credit.
-
E.
merchant cash advance–style product
A merchant cash advance–style product is a financing arrangement where a business receives an upfront lump sum in exchange for a contractually agreed portion of its future sales, typically repaid through automatic deductions from daily or weekly revenue.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:17 p.m.