Triple

T11093712
Position Surface form Disambiguated ID Type / Status
Subject Lendu language E262318 entity
Predicate hasEthnologueEntry P19233 FINISHED
Object Lendu E905404 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: Lendu | Statement: [Lendu language, hasEthnologueEntry, Lendu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lendu
Context triple: [Lendu language, hasEthnologueEntry, Lendu]
  • 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. Lubemba
    Lubemba is the traditional kingdom and cultural heartland of the Bemba people in what is now northern Zambia.
  • C. Wondunna
    Wondunna is a residential suburb located within the coastal city of Hervey Bay in Queensland, Australia.
  • D. Tallimba
    Tallimba is a small rural locality in the Riverina region of New South Wales, Australia, situated within an agricultural area west of the town of West Wyalong.
  • E. Sanglechi
    Sanglechi is a lesser-known Eastern Iranian language spoken in parts of northeastern Afghanistan and adjacent regions.
  • 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799ed12d88190a4ad8c346d68f11f completed April 9, 2026, 12:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69e441bb14d08190ac01bf3daa34ae43 completed April 19, 2026, 2:45 a.m.
Created at: April 8, 2026, 9:27 p.m.