Triple
T38332015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Assembly of Narok |
E1037847
|
entity |
| Predicate | budgetApprovedFor |
P112420
|
FINISHED |
| Object | Narok County Government |
—
|
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: Narok County Government | Statement: [County Assembly of Narok, budgetApprovedFor, Narok County Government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetApprovedFor Context triple: [County Assembly of Narok, budgetApprovedFor, Narok County Government]
-
A.
budgetApproval
Indicates that a proposed budget has been formally reviewed and granted permission to be implemented or spent.
-
B.
budgetApprovalRequiredFor
Indicates that obtaining approval for a budget is a necessary prerequisite for proceeding with the associated entity or activity.
-
C.
hasBudgetApprovedBy
Indicates that an entity’s budget has been formally reviewed and approved by a specified person or authority.
-
D.
authorizedBudget
chosen
Indicates that a specified budget amount has been formally approved for use by or for a particular entity or purpose.
-
E.
budgetPassedIs
Indicates that a proposed budget has been formally approved and passed.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7a4d7f881908b43b960911b81e9 |
completed | May 7, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69fcc589720c819089c8f500fea3c86a |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.