Triple

T18959727
Position Surface form Disambiguated ID Type / Status
Subject Tarn Taran Junction E463879 entity
Predicate connectsTo P845 FINISHED
Object Beas 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: Beas | Statement: [Tarn Taran Junction, connectsTo, Beas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beas
Context triple: [Tarn Taran Junction, connectsTo, Beas]
  • A. Beas chosen
    Beas is a town in the Amritsar district of Punjab, India, known for its spiritual significance as the headquarters of the Radha Soami Satsang Beas organization.
  • B. Beas River
    The Beas River is a major river in northern India that flows through the state of Punjab, playing a vital role in its agriculture and ecology.
  • C. Bhera
    Bhera is a historic town in present-day Punjab, Pakistan, known for its ancient trade routes and rich cultural heritage.
  • D. Kulu
    Kulu is a district and town in Turkey’s Central Anatolia region, known for its large expatriate community and strong ties to Europe, especially Sweden.
  • E. Bhavra
    Bhavra is a village in present-day Madhya Pradesh, India, historically notable as the birthplace of Indian revolutionary freedom fighter Chandrasekhar Azad.
  • 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5d1d784819095f3f886d7c47175 completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon