Triple
T22731070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Term Auction Facility |
E562133
|
entity |
| Predicate | peakOutstandingAmount |
P115031
|
FINISHED |
| Object | approximately $493 billion |
—
|
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: approximately $493 billion | Statement: [Term Auction Facility, peakOutstandingAmount, approximately $493 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakOutstandingAmount Context triple: [Term Auction Facility, peakOutstandingAmount, approximately $493 billion]
-
A.
paymentAmount
Indicates the specific monetary value involved in a payment transaction between parties.
-
B.
hasOutstandingValue
chosen
Indicates that an entity currently possesses an unpaid or unresolved amount, obligation, or worth that remains due or active.
-
C.
paysAfter
Indicates that one entity makes a payment to another entity only after a specified event, condition, or time has occurred.
-
D.
repaymentRequirement
Indicates that one party is obligated to pay back money or value to another party under specified terms or conditions.
-
E.
amountDependsOn
Indicates that the quantity or magnitude of one entity is determined by, or varies as a function of, 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_69e24550859c81908727d91efc3a81b4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1792de040819093aa904bf751a788 |
completed | April 29, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:21 p.m.