Triple
T23513823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Repayment Plan |
E572502
|
entity |
| Predicate | typicalRepaymentTerm |
P10122
|
FINISHED |
| Object | 10 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: 10 years | Statement: [Standard Repayment Plan, typicalRepaymentTerm, 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRepaymentTerm Context triple: [Standard Repayment Plan, typicalRepaymentTerm, 10 years]
-
A.
hasLongerRepaymentTermThan
Indicates that the repayment term of one entity (e.g., a loan or debt) is longer in duration than the repayment term of another entity.
-
B.
paymentPeriodLength
Indicates the duration or length of time that each payment period covers in a recurring payment or billing schedule.
-
C.
timeHorizonOfLoans
chosen
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
D.
numberOfMainInstallments
Indicates the total count of primary or scheduled installments associated with a given agreement, plan, or transaction.
-
E.
loanCharacteristic
Indicates that a loan possesses a specific attribute, feature, or quality that characterizes its terms or structure.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa80174c819088c9c19fdcf2a133 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.