Triple

T36741753
Position Surface form Disambiguated ID Type / Status
Subject Creek Indian territory E907637 entity
Predicate instanceOf P0 FINISHED
Object Muscogee (Creek) homeland C57694 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: Muscogee (Creek) homeland
Context triple: [Creek Indian territory, instanceOf, Muscogee (Creek) homeland]
  • A. Muscogee (Creek) cultural region chosen
    The Muscogee (Creek) cultural region encompasses the traditional homelands of the Muscogee people in the Southeastern United States, characterized by complex chiefdoms, mound-building traditions, riverine agriculture, and a rich ceremonial and linguistic heritage.
  • B. 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.
  • C. Muscogee people
    The Muscogee people, also known as the Creek, are a Native American nation originally from the Southeastern United States, with a distinct language, culture, and history shaped by complex alliances, forced removal, and contemporary tribal sovereignty.
  • D. Haudenosaunee territory
    Haudenosaunee territory refers to the traditional and contemporary lands inhabited, used, and governed by the Haudenosaunee Confederacy, spanning parts of what is now New York State, Ontario, and Quebec.
  • E. Seminole village
    A Seminole village is a traditional settlement of the Seminole people, typically composed of open-sided thatched chickee houses arranged around communal spaces in the wetlands and forests of Florida.
  • 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_69f76e76d10881909ec1679bc043108c completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:12 p.m.