Triple
T6245790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduated Repayment Plan |
E139717
|
entity |
| Predicate | finalPaymentLevel |
P42237
|
FINISHED |
| Object | higher than initial payments |
—
|
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: higher than initial payments | Statement: [Graduated Repayment Plan, finalPaymentLevel, higher than initial payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPaymentLevel Context triple: [Graduated Repayment Plan, finalPaymentLevel, higher than initial payments]
-
A.
isFinalInstallmentOf
Indicates that one work or item is the concluding or last part in a series, sequence, or collection of related works.
-
B.
finalValue
chosen
Indicates the resulting or ultimate value obtained after all relevant operations, changes, or calculations have been completed.
-
C.
finalPassing
Indicates that an entity successfully completes or passes a final evaluation, test, or stage in a process.
-
D.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
E.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
- 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.