Triple

T4632615
Position Surface form Disambiguated ID Type / Status
Subject Kunama people E101451 entity
Predicate autonym P1435 FINISHED
Object Kunama E108778 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: Kunama | Statement: [Kunama people, autonym, Kunama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kunama
Context triple: [Kunama people, autonym, Kunama]
  • A. Kunama chosen
    Kunama is a Nilo-Saharan language spoken primarily by the Kunama people in western Eritrea and adjacent parts of Ethiopia.
  • B. Kukawa
    Kukawa is a historic town in northeastern Nigeria that once served as the political and cultural center of the Kanuri people and the Bornu Empire.
  • C. Kuanua
    Kuanua is an Austronesian language spoken primarily by the Tolai people of East New Britain in Papua New Guinea.
  • D. Yanaon
    Yanaon is the former name of Yanam, a small coastal town in India that was once part of French India and retains a distinct Franco-Indian cultural heritage.
  • E. Wancho
    Wancho are an indigenous tribal community of northeastern India, primarily known for their distinct tattoos, woodcarving traditions, and vibrant festivals.
  • 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_69bd43d2f1c081908cd4b7ec48ecc73d completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a342ffc8190a911d0598ed230bb completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfabeba3c8190b6515b99746f62a6 completed March 21, 2026, 1:56 a.m.
Created at: March 20, 2026, 1:13 p.m.