Triple

T6053878
Position Surface form Disambiguated ID Type / Status
Subject Omaha tribe E134858 entity
Predicate hasAutonym P1435 FINISHED
Object Umoⁿhoⁿ E428716 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: Umoⁿhoⁿ | Statement: [Omaha tribe, hasAutonym, Umoⁿhoⁿ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Umoⁿhoⁿ
Context triple: [Omaha tribe, hasAutonym, Umoⁿhoⁿ]
  • A. Umoⁿhoⁿ chosen
    Umoⁿhoⁿ is the self-designated name of the Native American people commonly known in English as the Omaha.
  • B. Umana Yana
    Umana Yana is a traditional thatched benab-style conference and cultural hall in Georgetown, Guyana, originally built by Indigenous Wai-Wai people and now serving as a prominent national landmark and heritage site.
  • C. Ñuhu
    Ñuhu is the endonym used by the Otomi peoples to refer to themselves and their language within central Mexico.
  • D. Muhu
    Muhu is a large Estonian island in the Baltic Sea known for its traditional villages, distinctive folk culture, and role as a gateway between the mainland and Saaremaa.
  • E. Omyènè
    Omyènè is an alternative name for Myene, a Bantu language spoken primarily along the coast of Gabon.
  • 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_69c00877b6d4819096b0e163728b73a3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c05708fda48190ad3d1860969ebb6a completed March 22, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c113ac051c8190b2b8a4985948d8e0 completed March 23, 2026, 10:19 a.m.
Created at: March 22, 2026, 4:09 p.m.