Triple
T14315306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Washington (as a historic tribe) |
E354939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-level tribal designation |
C2272
|
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: state-level tribal designation Context triple: [State of Washington (as a historic tribe), instanceOf, state-level tribal designation]
-
A.
territorial designation
chosen
A territorial designation is a formal label or title that identifies and defines a specific geographic area or jurisdiction for political, administrative, or legal purposes.
-
B.
federally recognized tribe
A federally recognized tribe is a Native American or Alaska Native governing body that the U.S. federal government formally acknowledges as a sovereign political entity with a government-to-government relationship and eligibility for specific legal rights, services, and protections.
-
C.
state-level new area
A state-level new area is a specially designated development zone authorized by a provincial or equivalent government to pilot regional economic, social, and spatial reforms and drive coordinated urban-rural or cross-regional growth.
-
D.
federally designated region
A federally designated region is a geographic area formally defined and recognized by a national government for specific administrative, regulatory, programmatic, or statistical purposes.
-
E.
state-like entity
A state-like entity is an abstraction that encapsulates a distinct configuration of conditions or behaviors within a system, often determining how the system responds to inputs at a given time.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.