Triple
T19002328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Petr Nečas |
E464985
|
entity |
| Predicate | budgetPolicy |
P11306
|
FINISHED |
| Object | fiscal consolidation |
—
|
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: fiscal consolidation | Statement: [Government of Petr Nečas, budgetPolicy, fiscal consolidation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetPolicy Context triple: [Government of Petr Nečas, budgetPolicy, fiscal consolidation]
-
A.
budgetaryNature
Indicates that something pertains to, characterizes, or affects the allocation, management, or structure of a budget.
-
B.
budgetaryEffect
Indicates the financial impact or change in budget resulting from a particular action, decision, or policy.
-
C.
budgetFunction
Indicates a relationship where a specific budgeting rule or formula determines how resources or funds are allocated or constrained for an entity or activity.
-
D.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
E.
economicPolicyType
chosen
Indicates the classification of an economic policy according to its general type or category (e.g., fiscal, monetary, trade).
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d687cb2081909bf3ac761e292f22 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.