Triple
T6167212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extended Repayment Plan |
E137597
|
entity |
| Predicate | hasMaximumRepaymentTerm |
P10122
|
FINISHED |
| Object | 25 years |
—
|
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: 25 years | Statement: [Extended Repayment Plan, hasMaximumRepaymentTerm, 25 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumRepaymentTerm Context triple: [Extended Repayment Plan, hasMaximumRepaymentTerm, 25 years]
-
A.
timeHorizonOfLoans
chosen
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
B.
maximumBondMaturity
Indicates the longest allowable or actual time period until a bond tied to an entity reaches its maturity date.
-
C.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
D.
hasMainInstallment
Indicates that one entity is the primary or principal installment (e.g., main payment or main part of a series) associated with another entity.
-
E.
hasNoFixedTermLength
Indicates that the relationship or agreement exists without a predetermined or fixed duration for how long it will remain in effect.
- 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.