Triple

T2460893
Position Surface form Disambiguated ID Type / Status
Subject Desert Festival, Jaisalmer E54530 entity
Predicate heldIn P2777 FINISHED
Object Thar Desert E5064 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: Thar Desert | Statement: [Desert Festival, Jaisalmer, heldIn, Thar Desert]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thar Desert
Context triple: [Desert Festival, Jaisalmer, heldIn, Thar Desert]
  • A. Thar Desert chosen
    The Thar Desert is a vast arid region in northwestern India and eastern Pakistan, known for its sand dunes, extreme climate, and sparse vegetation.
  • B. Nefud Desert
    The Nefud Desert is a vast, crescent-shaped sand desert in northern Saudi Arabia known for its towering dunes and harsh, arid climate.
  • C. Błędów Desert
    Błędów Desert is a rare inland sand desert in southern Poland, known for its extensive dunes and unique, almost desert-like landscape.
  • D. Aralkum Desert
    The Aralkum Desert is a man-made desert that formed on the former seabed of the rapidly shrinking Aral Sea in Central Asia.
  • E. Ad Dahna Desert
    Ad Dahna Desert is a long, narrow corridor of reddish sand dunes in central Saudi Arabia that links the Nafud Desert in the north with the Rub' al Khali in the south.
  • 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_69ab49dee84c819096b50a0049c347ac completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd11c47408190b10c7f6a151f2db2 completed March 7, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69b108bf1214819091291de2c8343764 completed March 11, 2026, 6:16 a.m.
Created at: March 6, 2026, 9:44 p.m.