Triple
T23123054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PLUS Loan |
E576951
|
entity |
| Predicate | repaymentBegins |
P9379
|
FINISHED |
| Object | after full disbursement |
—
|
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: after full disbursement | Statement: [PLUS Loan, repaymentBegins, after full disbursement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repaymentBegins Context triple: [PLUS Loan, repaymentBegins, after full disbursement]
-
A.
repaymentTrigger
chosen
Indicates that a specific event or condition causes a repayment obligation to become due or activated.
-
B.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
C.
repaymentOutcome
Indicates the result or status of a repayment action, such as whether it was completed, failed, or partially fulfilled.
-
D.
debtFullyRepaidYear
Indicates the specific year in which a debt obligation has been completely repaid.
-
E.
effectiveForPaymentsMadeAfter
Indicates that a condition, rule, or agreement applies only to payments that are made after a specified time or event.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e517a0481909829a73fdf255d1c |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.