Triple

T23505816
Position Surface form Disambiguated ID Type / Status
Subject Kiranti E572278 entity
Predicate hasLanguage P15 FINISHED
Object Kulung 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: Kulung | Statement: [Kiranti, hasLanguage, Kulung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kulung
Context triple: [Kiranti, hasLanguage, Kulung]
  • A. Kulung Rai chosen
    Kulung Rai are an indigenous ethnolinguistic community of the eastern Himalayas, primarily in Nepal, known for their distinct Tibeto-Burman language and traditional Kirati cultural practices.
  • B. Lukung
    Lukung is a small village in the Ladakh region of India that serves as a gateway and popular stopover for visitors to the high-altitude Pangong Tso lake.
  • C. Kattang
    Kattang is an Aboriginal Australian language traditionally spoken by the Worimi people of New South Wales.
  • D. Kulon
    Kulon is an extinct Papuan language once spoken in the interior of West Papua, Indonesia.
  • E. Raklungu
    Raklungu is an indigenous local language spoken on Atauro Island, near Timor-Leste.
  • 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8ff97c88190a67f787e1674619e completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.