Triple

T20739788
Position Surface form Disambiguated ID Type / Status
Subject awa E509806 entity
Predicate secondaryRegion P26823 FINISHED
Object Nepal 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: Nepal | Statement: [awa, secondaryRegion, Nepal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nepal
Context triple: [awa, secondaryRegion, Nepal]
  • A. Nepal chosen
    Nepal is a landlocked South Asian country in the Himalayas, known for Mount Everest, its rich cultural heritage, and its location between India and China.
  • B. Bhutan
    Bhutan is a small, landlocked Himalayan kingdom in South Asia known for its Buddhist culture, mountainous landscapes, and emphasis on Gross National Happiness.
  • C. Gorkha, Nepal
    Gorkha, Nepal is a historic hill town in central Nepal known as the ancestral home of the Shah dynasty and a significant religious and cultural center.
  • D. Tibet
    Tibet is a high-altitude plateau region in Asia, historically known as the homeland of Tibetan Buddhism and the former Tibetan Empire, now an autonomous region of China.
  • E. Kangru
    Kangru is a small village located within Kiili Parish in northern Estonia.
  • 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20d9d4c8190a2fd87f8a33c313d completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:32 p.m.