Triple
T7461173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floating Rate Note |
E176251
|
entity |
| Predicate | principalRepayment |
P39808
|
FINISHED |
| Object | at maturity |
—
|
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: at maturity | Statement: [Floating Rate Note, principalRepayment, at maturity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalRepayment Context triple: [Floating Rate Note, principalRepayment, at maturity]
-
A.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
B.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
C.
repaymentTrigger
Indicates that a specific event or condition causes a repayment obligation to become due or activated.
-
D.
repaymentOutcome
Indicates the result or status of a repayment action, such as whether it was completed, failed, or partially fulfilled.
-
E.
hasMainInstallment
chosen
Indicates that one entity is the primary or principal installment (e.g., main payment or main part of a series) associated with 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d6cf8c8190a31cac121d151d78 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.