Triple
T6245794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduated Repayment Plan |
E139717
|
entity |
| Predicate | paymentBasedOn |
P35242
|
FINISHED |
| Object | repayment schedule |
—
|
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: repayment schedule | Statement: [Graduated Repayment Plan, paymentBasedOn, repayment schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentBasedOn Context triple: [Graduated Repayment Plan, paymentBasedOn, repayment schedule]
-
A.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
B.
billingMethod
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
-
C.
chargesBasedOn
chosen
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
D.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
E.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631d9e648190a59ab4001f506424 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.