Triple
T31995911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Ireland Assembly |
E816990
|
entity |
| Predicate | approvesBudgetFor |
P175334
|
FINISHED |
| Object | Department for the Economy |
—
|
NE NERFINISHED |
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: Department for the Economy | Statement: [Northern Ireland Assembly, approvesBudgetFor, Department for the Economy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvesBudgetFor Context triple: [Northern Ireland Assembly, approvesBudgetFor, Department for the Economy]
-
A.
budgetApproval
Indicates that a proposed budget has been formally reviewed and granted permission to be implemented or spent.
-
B.
hasBudgetApprovedBy
chosen
Indicates that an entity’s budget has been formally reviewed and approved by a specified person or authority.
-
C.
authorizedBudget
Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
-
D.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
E.
approvalFor
Indicates that one entity grants or has granted permission or consent for another entity’s action, request, or status.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 1, 2026, 12:13 a.m.