Triple
T8254699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee Constitution of 1827 |
E193043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cherokee Nation legal document |
C12618
|
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: Cherokee Nation legal document Context triple: [Cherokee Constitution of 1827, instanceOf, Cherokee Nation legal document]
-
A.
Muscogee tribal town
A Muscogee tribal town is a traditional socio-political and ceremonial community unit of the Muscogee (Creek) people, typically centered around a square ground and serving as a base for governance, ritual, and social life.
-
B.
Indigenous land rights document
chosen
A formal record that asserts, defines, or protects the legal and customary rights of Indigenous peoples to their traditional lands, territories, and resources.
-
C.
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.
-
D.
tribal nation
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
-
E.
Native American civil rights action
Native American civil rights action is organized legal, political, and grassroots efforts by Indigenous peoples and their allies to secure sovereignty, protect treaty rights, and achieve equal treatment under U.S. law and society.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:48 p.m.