Triple

T15890493
Position Surface form Disambiguated ID Type / Status
Subject Aka-Kede E385304 entity
Predicate relatedTo P37 FINISHED
Object Aka-Bo E318983 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: Aka-Bo | Statement: [Aka-Kede, relatedTo, Aka-Bo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aka-Bo
Context triple: [Aka-Kede, relatedTo, Aka-Bo]
  • A. Aka-Bo chosen
    Aka-Bo is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
  • B. Aka
    The Aka are a Central African Indigenous people known for their forest-based hunter-gatherer lifestyle and rich musical and cultural traditions.
  • C. 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.
  • D. Aka-Bale
    Aka-Bale is an extinct Great Andamanese language once spoken by the indigenous Aka-Bale people of the Andaman Islands in India.
  • E. Aka-Bea
    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.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1561e5ac481908ead7de3140c769d completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb59f979c8190826e35a16e295704 completed May 9, 2026, 10:30 p.m.
Created at: April 10, 2026, 4:51 a.m.