Triple
T35953201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution Funding Corporation |
E1039784
|
entity |
| Predicate | maximumAuthorizedDebt |
P125398
|
FINISHED |
| Object | $30 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: $30 billion | Statement: [Resolution Funding Corporation, maximumAuthorizedDebt, $30 billion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAuthorizedDebt Context triple: [Resolution Funding Corporation, maximumAuthorizedDebt, $30 billion]
-
A.
maximumLoanAmountUSD
Indicates the highest amount of money, expressed in U.S. dollars, that can be loaned under a given agreement or condition.
-
B.
maximumGrantAmount
Indicates the highest monetary value that can be awarded or granted under a specific grant, program, or agreement.
-
C.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
-
D.
deficitLimit
Indicates a constraint or maximum allowable amount on how large a deficit (shortfall or negative balance) may be.
-
E.
monetaryLimit
chosen
Indicates a constraint or maximum allowable amount of money associated with an action, transaction, or relationship.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:07 p.m.