Triple
T1043491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Note |
E22521
|
entity |
| Predicate | maximumAuthorizedAmount |
P7930
|
FINISHED |
| Object | 346,681,016 dollars |
—
|
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: 346,681,016 dollars | Statement: [United States Note, maximumAuthorizedAmount, 346,681,016 dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAuthorizedAmount Context triple: [United States Note, maximumAuthorizedAmount, 346,681,016 dollars]
-
A.
authorizedSpending
chosen
Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
-
B.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
C.
amendedLimit
Indicates that a previously established limit has been modified or updated from its original value.
-
D.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
E.
collateralRequired
Indicates that a party must provide collateral as a condition or security for an obligation, transaction, or agreement.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8475ab48190848388eea6448cb6 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.