Triple

T16051913
Position Surface form Disambiguated ID Type / Status
Subject Chief Mahaska E389371 entity
Predicate hasNameInEnglish P3437 FINISHED
Object Chief Mahaska E389371 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: Chief Mahaska | Statement: [Chief Mahaska, hasNameInEnglish, Chief Mahaska]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chief Mahaska
Context triple: [Chief Mahaska, hasNameInEnglish, Chief Mahaska]
  • A. Chief Mahaska chosen
    Chief Mahaska was a 19th-century leader of the Iowa (Ioway) people known for his role in relations with U.S. authorities during the era of westward expansion.
  • B. Chief Napi
    Chief Napi is a character based on a figure from Blackfoot mythology, depicted as a wise and powerful Native leader in the 2017 film "Wonder Woman."
  • C. Chief Paw-Hiu-Skah
    Chief Paw-Hiu-Skah was an Osage leader after whom the city of Pawhuska, Oklahoma, is named.
  • D. Chief Tannabok
    Chief Tannabok is the jovial and trusting leader of the city of El Dorado in the animated film "The Road to El Dorado."
  • E. Chief Petosega
    Chief Petosega was a 19th-century Odawa (Ottawa) leader in northern Michigan whose legacy is closely tied to the region around present-day Petoskey.
  • 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_69d86dae698881908327ef2d67706cb9 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183627bd88190bf94054de13a7733 completed April 17, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe478bcc48190bdd4fcb7ec51caad completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:56 a.m.