Triple

T9785571
Position Surface form Disambiguated ID Type / Status
Subject Limbu E237483 entity
Predicate language P15 FINISHED
Object Limbu language E763069 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: Limbu language | Statement: [Limbu, language, Limbu language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Limbu language
Context triple: [Limbu, language, Limbu language]
  • A. Limbu language chosen
    Limbu language is a Sino-Tibetan language spoken primarily by the Limbu ethnic group in eastern Nepal and neighboring regions of India.
  • B. Limbu
    Limbu are an indigenous ethnic group from eastern Nepal and neighboring regions, known for their distinct language, culture, and traditions within the broader Kirati community.
  • C. Murle language
    The Murle language is an Eastern Sudanic language spoken primarily by the Murle people of South Sudan.
  • D. Nilu Kurumba language
    The Nilu Kurumba language is a Dravidian tribal language spoken by the Nilu Kurumba people in parts of southern India, particularly in the Nilgiri region.
  • E. Logba language
    The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
  • 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_69ca84da927881909bda80caecad6010 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda2107f688190b2cab1509c508319 completed April 1, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1c4235ae88190aefaa6d9b63031e0 completed April 5, 2026, 2:08 a.m.
Created at: March 30, 2026, 8:27 p.m.