Triple

T18932121
Position Surface form Disambiguated ID Type / Status
Subject Ghaggar River E463138 entity
Predicate archaeologicalSitesAlong P108844 FINISHED
Object Banawali 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: Banawali | Statement: [Ghaggar River, archaeologicalSitesAlong, Banawali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banawali
Context triple: [Ghaggar River, archaeologicalSitesAlong, Banawali]
  • A. Banawali chosen
    Banawali is an archaeological site in Haryana, India, known for its well-preserved remains of the Indus Valley Civilization, including planned settlements and distinctive Harappan artifacts.
  • B. Balwa
    Balwa is a municipality-level city located in Nepal's Madhesh Province.
  • C. Saida Khera
    Saida Khera is a village in Punjab, India, known in folklore as a setting linked to the legendary love story of Heer Ranjha.
  • D. Daula
    Daula is a traditional double-headed drum central to Sri Lankan Kandyan dance and ritual music.
  • E. Ghulmet
    Ghulmet is a village located in the Nagar Valley of Gilgit-Baltistan in northern Pakistan, known for its mountainous terrain and scenic surroundings.
  • 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_69d8dcfec90481909e926be9767e5779 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c9c0b84881909ad6da9522203df8 completed April 20, 2026, 6:37 a.m.
Created at: April 10, 2026, 11:59 a.m.