Triple

T22877467
Position Surface form Disambiguated ID Type / Status
Subject Wasilla, Alaska E567363 entity
Predicate namedAfter P63 FINISHED
Object Chief Wasilla NE NERFINISHED

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: Chief Wasilla | Statement: [Wasilla, Alaska, namedAfter, Chief Wasilla]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chief Wasilla
Context triple: [Wasilla, Alaska, namedAfter, Chief Wasilla]
  • A. Chief Wasilla chosen
    Chief Wasilla was a local Dena'ina Athabascan leader in southcentral Alaska whose name was later given to the city of Wasilla.
  • B. Chief Leschi
    Chief Leschi was a 19th-century Nisqually leader known for resisting U.S. encroachment on his people's lands and becoming a symbol of Native American resistance and injustice in the Pacific Northwest.
  • C. Chief Wasso
    Chief Wasso was a Native American leader after whom the city of Owosso, Michigan, is named.
  • D. Chief Tintic
    Chief Tintic was a 19th-century Ute leader in central Utah whose name became associated with the region’s rich mining district.
  • E. Chief Toke
    Chief Toke was a 19th-century leader of the Shoalwater Bay (Willapa) people in what is now southwestern Washington State, remembered for his role in local tribal history and as the namesake of Tokeland.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24589d8348190b96422d13a678bc1 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17f5966c08190a9ded9b19b166112 completed April 29, 2026, 3:47 a.m.
Created at: April 17, 2026, 3:39 p.m.