Triple
T6167223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Repayment Plan |
E137597
|
entity |
| Predicate | repaymentTermRange |
P10122
|
FINISHED |
| Object | 12 to 25 years depending on loan balance |
—
|
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: 12 to 25 years depending on loan balance | Statement: [Extended Repayment Plan, repaymentTermRange, 12 to 25 years depending on loan balance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repaymentTermRange Context triple: [Extended Repayment Plan, repaymentTermRange, 12 to 25 years depending on loan balance]
-
A.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
B.
timeHorizonOfLoans
chosen
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
C.
repaymentTrigger
Indicates that a specific event or condition causes a repayment obligation to become due or activated.
-
D.
leasePeriod
Indicates the duration or time span for which a lease agreement is valid between parties.
-
E.
fundingPeriod
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d647ae48190a1db07b4f4a06e67 |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.