Triple

T19018971
Position Surface form Disambiguated ID Type / Status
Subject Bijwasan E465430 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Samalkha 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: Samalkha | Statement: [Bijwasan, hasNeighbourhood, Samalkha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Samalkha
Context triple: [Bijwasan, hasNeighbourhood, Samalkha]
  • A. Samalkha chosen
    Samalkha is a town in the northern Indian state of Haryana, known for its industrial activity and location along major transport routes.
  • B. Serakhulle
    Serakhulle refers to the Soninke people, a West African ethnic group historically known for their role in the ancient Ghana Empire and long-distance trade.
  • C. Shimsha
    Shimsha is a river in southern India that flows through Karnataka and is known for its waterfalls and contribution to the Kaveri river system.
  • D. Shandar
    Shandar was a French avant-garde record label known for releasing experimental and free jazz recordings in the 1970s.
  • E. Melaghar
    Melaghar is a town in the Indian state of Tripura known as the gateway to the historic Neermahal water palace and its surrounding lake.
  • 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_69d8dd025c188190a1d81f5b4ec7e2c6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6dd0e6c8190a6dc6af1f7901299 completed April 20, 2026, 7:33 a.m.
Created at: April 10, 2026, 12:02 p.m.