Triple
T16493372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brady Plan |
E400621
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sovereign debt restructuring program |
C37538
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: sovereign debt restructuring program Context triple: [Brady Plan, instanceOf, sovereign debt restructuring program]
-
A.
sovereign default event
A sovereign default event is the failure or restructuring by a national government to meet its debt obligations as originally agreed, triggering legal, financial, and market consequences.
-
B.
U.S. Treasury debt collection program
A U.S. Treasury debt collection program is a federal initiative that centralizes and enforces the collection of delinquent debts owed to government agencies through tools such as offsets, payment arrangements, and legal actions.
-
C.
concordato
A concordato is a formal agreement, often in legal or financial contexts, that restructures obligations or settles disputes between parties, typically to avoid more severe consequences like bankruptcy or prolonged litigation.
-
D.
organ of the European Stability Mechanism
An organ of the European Stability Mechanism is a formal decision-making or oversight body within the ESM’s institutional structure, endowed with specific powers and responsibilities to ensure its effective governance and operation.
-
E.
currency realignment accord
A currency realignment accord is a formal agreement between countries or monetary authorities to adjust exchange rates or related policies in order to correct imbalances and stabilize international financial relationships.
- F. None of above. chosen
Provenance (1 batch)
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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:13 a.m.