Triple
T22675035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Term Securities Lending Facility |
E560322
|
entity |
| Predicate | settlementFrequency |
P41187
|
FINISHED |
| Object | weekly |
—
|
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: weekly | Statement: [Term Securities Lending Facility, settlementFrequency, weekly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementFrequency Context triple: [Term Securities Lending Facility, settlementFrequency, weekly]
-
A.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
-
B.
settlementPattern
Indicates how human dwellings or communities are spatially arranged and distributed across a geographic area.
-
C.
payFrequency
chosen
Indicates how often a payment or series of payments is made within a given time period.
-
D.
associatedSettlementPeriod
Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
-
E.
settlementTerm
Indicates the agreed conditions, timing, and method by which an obligation, transaction, or dispute is settled between parties.
- 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.