Triple
T7492870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Commissioner of Tabora |
E177049
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional commissioner |
C1183
|
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 commissioner Context triple: [Regional Commissioner of Tabora, instanceOf, regional commissioner]
-
A.
regional directors
Regional directors are senior managers responsible for overseeing operations, strategy implementation, and performance across multiple locations within a defined geographic area.
-
B.
Chief Commissioner's Province
A Chief Commissioner's Province is a type of administrative division in which a territory is governed directly by a chief commissioner appointed by a central authority, rather than by a locally elected government.
-
C.
regional administrative branch
chosen
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.
-
D.
territorial governor in the United States
A territorial governor in the United States was a federally appointed executive who administered a U.S. territory before it achieved statehood, overseeing local government, law enforcement, and relations with the federal government.
-
E.
regional planner
A regional planner is a professional who analyzes and coordinates land use, infrastructure, resources, and policies across multiple communities or jurisdictions to guide sustainable and balanced regional development.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:43 p.m.