Triple
T12029334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraq Liberation Act |
E286359
|
entity |
| Predicate | authorizedFundingCeiling |
P37671
|
FINISHED |
| Object | $97,000,000 |
—
|
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: $97,000,000 | Statement: [Iraq Liberation Act, authorizedFundingCeiling, $97,000,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedFundingCeiling Context triple: [Iraq Liberation Act, authorizedFundingCeiling, $97,000,000]
-
A.
fundingCapType
Indicates the classification or category of a limit placed on the amount of funding that can be provided.
-
B.
maximumGrantAmount
chosen
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.
guaranteeLimitBasis
Indicates the basis or criteria used to determine the limit of a guarantee in a contractual or financial context.
-
E.
authorizedBondAmount
Indicates the maximum bond value that has been formally approved or permitted for issuance or use in a given context.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.