Triple

T15647625
Position Surface form Disambiguated ID Type / Status
Subject Gorkha District E376221 entity
Predicate hasCapital P204 FINISHED
Object Gorkha E192472 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: Gorkha | Statement: [Gorkha District, hasCapital, Gorkha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gorkha
Context triple: [Gorkha District, hasCapital, Gorkha]
  • A. Gurung
    Gurung is a Sino-Tibetan language spoken primarily by the Gurung ethnic community from the Himalayan regions of Nepal and its diaspora, including Nepali Americans.
  • B. Sugauli
    Sugauli is a town in the Indian state of Bihar historically known as the place where the 1816 Treaty of Sugauli between the British East India Company and Nepal was concluded.
  • C. Banepa
    Banepa is a historic Newar-influenced town in central Nepal known as a local commercial hub and cultural center.
  • D. Thakuri
    Thakuri is a high-status Khas caste group of Nepal traditionally associated with nobility and ruling elites.
  • E. Gorkha Kingdom chosen
    The Gorkha Kingdom was a historic Himalayan state that unified much of what is now Nepal and became a major regional power before confronting the British East India Company in the early 19th century.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed5b8b081908d7127964eed3b09 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff67936e388190913c9060194e5b53 completed May 9, 2026, 4:57 p.m.
Created at: April 10, 2026, 4:15 a.m.