Triple

T15450740
Position Surface form Disambiguated ID Type / Status
Subject Costanoan E370142 entity
Predicate hasLanguage P15 FINISHED
Object Awaswas E362271 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Awaswas | Statement: [Costanoan, hasLanguage, Awaswas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Awaswas
Context triple: [Costanoan, hasLanguage, Awaswas]
  • A. Awaswas chosen
    Awaswas is an extinct Ohlone (Costanoan) Native American language once spoken along the central coast of California.
  • B. Waapakoneta
    Waapakoneta is the Native American (likely Shawnee) settlement and name from which the modern city of Wapakoneta, Ohio, derives its origin.
  • C. Hoocąk
    Hoocąk is the endonym for the Ho-Chunk people, a Native American nation originally from the Wisconsin and Illinois regions of the United States.
  • D. Kaska
    Kaska is an Athabaskan Indigenous language traditionally spoken by the Kaska Dena people of northern Canada, primarily in the Yukon and northern British Columbia.
  • E. Obedjiwan
    Obedjiwan is an Atikamekw First Nations community located in a remote area of central Quebec, Canada.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03efaf82c81908b464e37ce9c159a completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff21b1e9688190a283dbc552072ce0 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:21 a.m.