Triple
T1699768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regering der Nederlanden |
E36740
|
entity |
| Predicate | usesBudget |
P27969
|
FINISHED |
| Object | Rijksbegroting van Nederland |
—
|
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: Rijksbegroting van Nederland | Statement: [Regering der Nederlanden, usesBudget, Rijksbegroting van Nederland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBudget Context triple: [Regering der Nederlanden, usesBudget, Rijksbegroting van Nederland]
-
A.
usesSalaryBudgets
Indicates that one entity allocates or manages financial resources for compensation based on predefined salary budgets associated with another entity.
-
B.
budgetFrom
chosen
Indicates that a budget or funding allocation originates from or is provided by a particular source.
-
C.
budgetRight
Indicates that an entity has the authority, responsibility, or entitlement to allocate, manage, or decide on the use of a specified budget or financial resources.
-
D.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
E.
budgetType
Indicates the classification or category of a budget associated with an entity or financial activity.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.