Triple
T22675046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Term Securities Lending Facility |
E560322
|
entity |
| Predicate | maximumProgramSize |
P149194
|
FINISHED |
| Object | 200000000000 USD |
—
|
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: 200000000000 USD | Statement: [Term Securities Lending Facility, maximumProgramSize, 200000000000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumProgramSize Context triple: [Term Securities Lending Facility, maximumProgramSize, 200000000000 USD]
-
A.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
B.
maxStackSize
Indicates the maximum number of identical items or elements that can be grouped or stacked together as a single unit.
-
C.
maximumPackSize
Indicates the largest number of items or units that are allowed or intended to be grouped together in a single pack.
-
D.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
E.
maxNumberOfProcessors
Indicates the maximum number of processors that are allowed or supported in a given context or configuration.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.