Triple
T29715746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lwengo District |
E751902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub-national administrative unit |
C740
|
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: sub-national administrative unit Context triple: [Lwengo District, instanceOf, sub-national administrative unit]
-
A.
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.
-
B.
sub-prefecture
A sub-prefecture is an administrative division below the level of a prefecture, typically overseen by a sub-prefect and responsible for local governance and implementation of national or regional policies within its territory.
-
C.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
D.
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.
-
E.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
- F. None of above.
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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:33 p.m.