Triple

T20667808
Position Surface form Disambiguated ID Type / Status
Subject Mount Everest E507937 entity
Predicate locatedOnBorderOf P224 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: [Mount Everest, locatedOnBorderOf, Nepal]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nepal
Context triple: [Mount Everest, locatedOnBorderOf, 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_69e0b4c059bc81908ea762cd73ea4424 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6b5c4c4608190ae17da4a59e5ae80 completed April 20, 2026, 11:24 p.m.
Created at: April 16, 2026, 11:44 a.m.