Triple
T1027324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Alaska |
E22168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil and military administrative district |
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: civil and military administrative district Context triple: [District of Alaska, instanceOf, civil and military administrative district]
-
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.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
C.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
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.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.