Triple

T21478532
Position Surface form Disambiguated ID Type / Status
Subject Bijbehara E529924 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Awantipora NE NERFINISHED

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: Awantipora | Statement: [Bijbehara, hasNearbySettlement, Awantipora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Awantipora
Context triple: [Bijbehara, hasNearbySettlement, Awantipora]
  • A. Awantipora chosen
    Awantipora is a town in the Kashmir Valley of Jammu and Kashmir, India, known for its historic Awantipora temple ruins and scenic location along the Jhelum River.
  • B. Tanakpur
    Tanakpur is a small town in Uttarakhand, India, known as a gateway to the Kumaon region and a key transit point to the neighboring country of Nepal.
  • C. Nawalgarh
    Nawalgarh is a historic town in Rajasthan, India, renowned for its richly painted havelis and cultural heritage within the Shekhawati region.
  • D. Nagaur
    Nagaur is a historic city in Rajasthan, India, known for its medieval fort, cultural heritage, and role as an important center in the Marwar region.
  • E. Ranakpur
    Ranakpur is a village in Rajasthan, India, renowned for its intricately carved Jain temples and stunning marble architecture set amid the Aravalli hills.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c45acc3881908e38d3f28964152b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea1951fc8190910f634327aa5c3f completed April 23, 2026, 9:44 a.m.
Created at: April 16, 2026, 6:20 p.m.