Triple
T24993638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty on Stability, Coordination and Governance |
E625510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fiscal compact |
C18705
|
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: fiscal compact Context triple: [Treaty on Stability, Coordination and Governance, instanceOf, fiscal compact]
-
A.
fiscal commission
A fiscal commission is an appointed body of experts tasked with analyzing a government’s budgetary situation and recommending policies to improve fiscal sustainability and balance public finances.
-
B.
fiscal federalism institution
A fiscal federalism institution is an organization or framework that designs, manages, and oversees the allocation of taxing powers, revenue sharing, and intergovernmental transfers among different levels of government within a federal system.
-
C.
fiscal policy program
A fiscal policy program is a coordinated set of government actions and rules that use taxation, spending, and borrowing to influence economic activity, growth, and stability.
-
D.
fiscal policy document
A fiscal policy document is an official record that outlines a government or organization’s strategies, rules, and decisions regarding taxation, spending, and budgeting to achieve economic and financial objectives.
-
E.
public finance legislation
chosen
Public finance legislation comprises the body of laws and regulations that govern how governments raise revenue, allocate expenditures, manage public debt, and oversee fiscal responsibility to achieve economic and social policy objectives.
- F. None of above.
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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:04 a.m.