Triple

T9921446
Position Surface form Disambiguated ID Type / Status
Subject Kongde Ri E187804 entity
Predicate hasSummit P8024 FINISHED
Object Kongde North E187804 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: Kongde North | Statement: [Kongde Ri, hasSummit, Kongde North]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kongde North
Context triple: [Kongde Ri, hasSummit, Kongde North]
  • A. Kongde Ri chosen
    Kongde Ri is a prominent Himalayan peak in Nepal known for its striking multi-summited massif overlooking the Everest region.
  • B. Diqing
    Diqing is an autonomous prefecture in northwestern Yunnan Province, China, known for its Tibetan culture, high-altitude landscapes, and proximity to the eastern Himalayas.
  • C. Dayong
    Dayong is the former name of the city now known as Zhangjiajie in Hunan Province, China, famed for its dramatic sandstone pillar landscapes.
  • D. Yecheng
    Yecheng was an important ancient Chinese city that served as a major political and cultural center in northern China during several dynasties.
  • E. Tingkhong
    Tingkhong is a notable town in the Indian state of Assam, recognized as one of the key urban centers within Dibrugarh district.
  • 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_69ca82b22a688190b52c75bd48429c10 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb56abbb88190a21b8b77f1a25b81 completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20e019f788190a0106b60c8a39efa completed April 5, 2026, 7:23 a.m.
Created at: March 30, 2026, 8:42 p.m.