Triple

T16182432
Position Surface form Disambiguated ID Type / Status
Subject Aka-Bale E392716 entity
Predicate relatedTo P37 FINISHED
Object Aka-Kede E385304 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-Kede | Statement: [Aka-Bale, relatedTo, Aka-Kede]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aka-Kede
Context triple: [Aka-Bale, relatedTo, Aka-Kede]
  • A. Aka-Kede chosen
    Aka-Kede is an extinct Great Andamanese language once spoken by an indigenous community in the Andaman Islands of India.
  • 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-Kora
    Aka-Kora is an extinct Great Andamanese language once spoken by the Kora people of North Andaman Island 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 (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_69d87f1e49ac8190a311b54d32990576 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e2205ef39081908da383abdebc2ccc completed April 17, 2026, 11:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0007899b408190abcb7e72bdc81e9d completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 5:02 a.m.