Triple

T8943512
Position Surface form Disambiguated ID Type / Status
Subject Tura E212962 entity
Predicate hasNearbyAttraction P2064 FINISHED
Object Tura Peak E768182 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: Tura Peak | Statement: [Tura, hasNearbyAttraction, Tura Peak]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tura Peak
Context triple: [Tura, hasNearbyAttraction, Tura Peak]
  • A. Tura Peak chosen
    Tura Peak is a prominent hilltop and popular viewpoint in the Garo Hills of Meghalaya, India, known for its scenic landscapes and trekking opportunities.
  • B. Chembra Peak
    Chembra Peak is a popular trekking destination and one of the highest peaks in Kerala’s Western Ghats, known for its scenic views and heart-shaped lake.
  • C. Trikuta Hill
    Trikuta Hill is a prominent sandstone hill in Jaisalmer, Rajasthan, known as the elevated site on which the historic Jaisalmer Fort stands.
  • D. Doddabetta Peak
    Doddabetta Peak is the highest mountain in the Nilgiri Hills of Tamil Nadu, India, offering panoramic views and a popular viewpoint near Ooty.
  • E. Garhshankar
    Garhshankar is a town and municipal council in the Hoshiarpur district of the Indian state of Punjab.
  • 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_69ca839694c88190b324ffeb43d23b08 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66da71808190b4454b2f95aae0bd completed April 1, 2026, 12:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfd099b2f48190b81d6747bad4b992 completed April 3, 2026, 2:37 p.m.
Created at: March 30, 2026, 6:58 p.m.