Triple

T23355681
Position Surface form Disambiguated ID Type / Status
Subject Adi people E593040 entity
Predicate language P15 FINISHED
Object Adi language 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: Adi language | Statement: [Adi people, language, Adi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adi language
Context triple: [Adi people, language, Adi language]
  • A. Adi language chosen
    The Adi language is a Tibeto-Burman language spoken primarily by the Adi people of Arunachal Pradesh in northeastern India.
  • B. Adiyan language
    The Adiyan language is a lesser-known Dravidian language spoken by the Adiyan tribal community, primarily in parts of southern India.
  • C. Andio language
    The Andio language is an Austronesian language spoken by a small community in Central Sulawesi, Indonesia, and is part of the Celebic subgroup.
  • D. Bafia language
    The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
  • E. Andi language
    The Andi language is a Northeast Caucasian language spoken by the Andi people in the western part of Dagestan, Russia.
  • 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_69e25d24d2a4819092e6ede74c2a918d completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f19a176b548190bf5a08bb2585344d completed April 29, 2026, 5:41 a.m.
Created at: April 17, 2026, 5:26 p.m.