Triple

T3622330
Position Surface form Disambiguated ID Type / Status
Subject Ladakh E76754 entity
Predicate hasLanguage P15 FINISHED
Object Balti E77468 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: Balti | Statement: [Ladakh, hasLanguage, Balti]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balti
Context triple: [Ladakh, hasLanguage, Balti]
  • A. Balti chosen
    Balti is a Tibetic language spoken primarily in the Baltistan region of northern Pakistan and parts of Ladakh, India.
  • B. Bakkhali
    Bakkhali is a seaside town and beach resort on the Bay of Bengal in the Indian state of West Bengal, known for its tranquil beaches and scenic coastal views.
  • C. Khinkali
    Khinkali is a popular Georgian dumpling typically filled with spiced meat and broth, known for its distinctive twisted top and eaten by hand.
  • D. Rozogi
    Rozogi is a village in northern Poland that serves as a local administrative and service center within the Warmian-Masurian Voivodeship.
  • E. Meehni
    Meehni is one of the three iconic sandstone rock pillars known as the Three Sisters in the Blue Mountains of New South Wales, Australia.
  • 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_69ad85dae2fc81908d1ceadbc6af0089 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc2bb12cc8190bd67597cf3b66a3a completed March 8, 2026, 6:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69b43320955c8190910c0f15c80f41f4 completed March 13, 2026, 3:54 p.m.
Created at: March 8, 2026, 3:23 p.m.