Triple

T17378247
Position Surface form Disambiguated ID Type / Status
Subject Aka-Bea language E422497 entity
Predicate ethnicity P194 FINISHED
Object Aka-Bea 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: Aka-Bea | Statement: [Aka-Bea language, ethnicity, Aka-Bea]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aka-Bea
Context triple: [Aka-Bea language, ethnicity, Aka-Bea]
  • A. Aka-Bea chosen
    Aka-Bea is an extinct Great Andamanese language once spoken by the indigenous Aka-Bea people of the Andaman Islands in the Bay of Bengal.
  • B. Aka-Bale
    Aka-Bale is an extinct Great Andamanese language once spoken by the indigenous Aka-Bale people of the Andaman Islands in India.
  • C. Aka-Bo
    Aka-Bo is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
  • D. Aka
    The Aka are a Central African Indigenous people known for their forest-based hunter-gatherer lifestyle and rich musical and cultural traditions.
  • E. Aka
    The Aka are an indigenous ethnic group of the eastern Himalayas, traditionally inhabiting parts of Arunachal Pradesh in northeastern India, including the Bomdila region.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a6ea56c8190b56d966ccf2c91f7 completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:45 a.m.