Triple

T11697144
Position Surface form Disambiguated ID Type / Status
Subject Ama Dablam E278024 entity
Predicate hasParentPeak P1319 FINISHED
Object Kangtega E830528 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: Kangtega | Statement: [Ama Dablam, hasParentPeak, Kangtega]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kangtega
Context triple: [Ama Dablam, hasParentPeak, Kangtega]
  • A. Kangtega chosen
    Kangtega is a prominent Himalayan peak in Nepal’s Khumbu region, known for its distinctive saddle-shaped summit and challenging climbing routes.
  • B. Gangte
    Gangte is a Kuki-Chin language spoken primarily by the Gangte people in parts of Northeast India, especially in Manipur.
  • C. Kattang
    Kattang is an Aboriginal Australian language traditionally spoken by the Worimi people of New South Wales.
  • D. Piankhi
    Piankhi, also known as Piye, was an ancient Nubian king who founded Egypt’s Twenty-fifth Dynasty and is noted for unifying Egypt under Kushite rule in the 8th century BCE.
  • E. Lamkang
    Lamkang is a Tibeto-Burman language spoken by the Lamkang people, primarily in parts of Northeast India and Myanmar.
  • 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_69d6aafe02d881909900d54ad7d4af84 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a47cef60819088b7cc3a3a711e4c completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69f01943196c8190900b46da238e1f24 completed April 28, 2026, 2:19 a.m.
Created at: April 8, 2026, 9:40 p.m.