Triple
T21092022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VA Home Loan Guaranty Program |
E519659
|
entity |
| Predicate | fundingFee |
P117840
|
FINISHED |
| Object | may be financed into the loan amount |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: may be financed into the loan amount | Statement: [VA Home Loan Guaranty Program, fundingFee, may be financed into the loan amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingFee Context triple: [VA Home Loan Guaranty Program, fundingFee, may be financed into the loan amount]
-
A.
fundingCost
Indicates the financial expense or resources required to provide funding for an entity, project, or activity.
-
B.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
-
C.
transactionFees
Indicates the fees charged or incurred as part of executing a financial transaction between parties.
-
D.
baseFee
chosen
Indicates the standard, initial fee amount applied before any additional charges, discounts, or adjustments.
-
E.
feeMarketChange
Indicates a change or adjustment in a fee market, such as an update to prevailing fees or fee structure within that market.
- F. None of above.
Provenance (3 batches)
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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:51 p.m.