Triple

T10815801
Position Surface form Disambiguated ID Type / Status
Subject Kongur Tagh E255223 entity
Predicate hasSubpeak P7612 FINISHED
Object Kongur Ti E889139 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: Kongur Ti | Statement: [Kongur Tagh, hasSubpeak, Kongur Ti]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kongur Ti
Context triple: [Kongur Tagh, hasSubpeak, Kongur Ti]
  • A. Kongur Ti chosen
    Kongur Ti is an alternate name for Kongur Tagh, a prominent and glaciated mountain massif in China’s Pamir–Kunlun region and one of the highest peaks in the world.
  • B. Kungara
    Kungara is an alternative name for the Fur language, a Nilo-Saharan language spoken primarily by the Fur people of western Sudan.
  • C. Koni
    Koni is a diminutive form of the given name Konrad, typically used as an affectionate nickname.
  • D. Kango
    Kango is a town in western Gabon known as a transport hub along the N1 road and a gateway between the capital Libreville and the interior regions.
  • E. Rongker
    Rongker is a traditional religious and agricultural festival of the Karbi people in Northeast India, celebrated to seek blessings for prosperity, good harvests, and communal well-being.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d733edab248190b2cf7f7bc2684468 completed April 9, 2026, 5:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69dff7c45f288190a5235b5d7000a32c completed April 15, 2026, 8:40 p.m.
Created at: April 8, 2026, 9:18 p.m.