Triple

T21326791
Position Surface form Disambiguated ID Type / Status
Subject Lendu people E525778 entity
Predicate hasAutonym P1435 FINISHED
Object BaLendu 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: BaLendu | Statement: [Lendu people, hasAutonym, BaLendu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: BaLendu
Context triple: [Lendu people, hasAutonym, BaLendu]
  • A. Lendu-Bale chosen
    Lendu-Bale is an alternative name for the Lendu language, a Central Sudanic language spoken primarily in the northeastern Democratic Republic of the Congo.
  • B. Ballu
    Ballu is a French surname most notably associated with architect Albert Ballu.
  • C. Balara
    Balara is a municipality-level city in southeastern Nepal’s Madhesh Province, known for its agrarian economy and proximity to the Indian border.
  • D. Bonalu
    Bonalu is a traditional Hindu folk festival of Telangana centered on the worship of the goddess Mahakali, marked by colorful processions, ritual offerings, and regional music and dance.
  • E. Balantak
    Balantak is an Austronesian language of central Sulawesi, Indonesia, closely related to and often grouped with the Saluan language.
  • 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_69e0b51b90788190a4dd823d962626da completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7ab4a796081908148ec9106362d3d completed April 21, 2026, 4:52 p.m.
Created at: April 16, 2026, 4:41 p.m.