Triple

T18959716
Position Surface form Disambiguated ID Type / Status
Subject Tarn Taran Junction E463879 entity
Predicate serves P98 FINISHED
Object Tarn Taran town 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: Tarn Taran town | Statement: [Tarn Taran Junction, serves, Tarn Taran town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarn Taran town
Context triple: [Tarn Taran Junction, serves, Tarn Taran town]
  • A. Tarn Taran chosen
    Tarn Taran is a historic town in the Majha region of Punjab, India, known for its significant Sikh religious heritage and prominent gurdwaras.
  • B. Beas town
    Beas town is a small settlement in the Indian state of Punjab, known primarily for its proximity to the Beas River and the headquarters of the Radha Soami Satsang Beas spiritual organization.
  • C. Taranagar
    Taranagar is a town in the Churu district of Rajasthan, India, known for its regional trade, educational institutions, and cultural heritage.
  • D. Naharkatiya town
    Naharkatiya town is a settlement in Assam, India, known for its proximity to one of the region’s earliest and most significant oil-producing areas.
  • E. Tarn Taran district
    Tarn Taran district is an administrative district in the Indian state of Punjab, known for its agricultural landscape and proximity to the Beas River.
  • 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