Triple
T26132910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Revenue and Expenditure Budget (APBD DKI Jakarta) |
E659299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional government budget |
C51150
|
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: regional government budget Context triple: [Regional Revenue and Expenditure Budget (APBD DKI Jakarta), instanceOf, regional government budget]
-
A.
regional government service
A regional government service is an administrative entity that delivers public programs, resources, and regulatory functions within a specific geographic area under the authority of a higher-level government.
-
B.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
C.
sub‑national government
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial jurisdiction.
-
D.
regional politics
Regional politics is the study and practice of how political power, policies, and relationships operate within and between specific geographic areas or subnational units, such as states, provinces, or regions.
-
E.
regional election
A regional election is a formal process in which eligible voters within a specific subnational area (such as a state, province, or region) choose representatives or leaders for regional governing bodies.
- F. None of above. chosen
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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:15 p.m.