Triple

T10406448
Position Surface form Disambiguated ID Type / Status
Subject Pusa, Bihar E245274 entity
Predicate locatedNear P294 FINISHED
Object Darbhanga E850828 NE FINISHED

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: Darbhanga | Statement: [Pusa, Bihar, locatedNear, Darbhanga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Darbhanga
Context triple: [Pusa, Bihar, locatedNear, Darbhanga]
  • A. Darbhanga chosen
    Darbhanga is a major city in the Indian state of Bihar, known as a cultural and educational center of the Mithila region.
  • B. Buxar
    Buxar is a historic town in the Indian state of Bihar, best known as the site of a pivotal 1764 battle that cemented British colonial dominance in northern India.
  • C. Rampurhat
    Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
  • D. Purnea
    Purnea is a prominent city in the Indian state of Bihar, known as a commercial and educational hub for the surrounding northeastern region.
  • E. Lakhnauti
    Lakhnauti is the medieval name of the historic city of Gaur, a major political and cultural center of the Bengal Sultanate in eastern India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d381be340c8190b05998703d42d224 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e9f834288190a0df246974ffaea8 completed April 7, 2026, 11:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69d95e5197cc8190ad70c665ec2f8fa8 completed April 10, 2026, 8:32 p.m.
Created at: April 6, 2026, 12:08 p.m.