Triple
T28069490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwestern Region (USFS Region 3) |
E709353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government administrative region |
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: government administrative region Context triple: [Southwestern Region (USFS Region 3), instanceOf, government administrative region]
-
A.
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.
-
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.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
D.
federal administrative unit
A federal administrative unit is a territorial or organizational subdivision within a federal state that carries out governmental functions and implements policies under the authority of the national government.
-
E.
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.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:45 p.m.