Triple
T22675033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Term Securities Lending Facility |
E560322
|
entity |
| Predicate | loanMaturity |
P10122
|
FINISHED |
| Object | 28 days |
—
|
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: 28 days | Statement: [Term Securities Lending Facility, loanMaturity, 28 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loanMaturity Context triple: [Term Securities Lending Facility, loanMaturity, 28 days]
-
A.
maturityDuration
Indicates the length of time required for something to reach its full development, readiness, or maturity.
-
B.
maturesIn
Indicates that an entity reaches full development, ripeness, or maturity within a specified time period or under certain conditions.
-
C.
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.
-
D.
timeHorizonOfLoans
chosen
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
E.
hasMaturityDate
Indicates the date on which an obligation, instrument, or agreement is scheduled to become due or reach the end of its term.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17823bd1881908958b0a8ba59e199 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.