Triple

T19310000
Position Surface form Disambiguated ID Type / Status
Subject Kalkaji Mandir E482938 entity
Predicate near P350 FINISHED
Object Govindpuri 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: Govindpuri | Statement: [Kalkaji Mandir, near, Govindpuri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Govindpuri
Context triple: [Kalkaji Mandir, near, Govindpuri]
  • A. Govindpuri chosen
    Govindpuri is a densely populated residential neighborhood in South Delhi, India, known for its urban markets, metro connectivity, and proximity to major commercial and educational hubs.
  • B. Gadarpur
    Gadarpur is a town in the Udham Singh Nagar district of Uttarakhand, India, known primarily as an agricultural and trading center in the Terai region.
  • C. Mangolpuri
    Mangolpuri is a densely populated residential and industrial neighborhood located in the North West part of Delhi, India.
  • D. Surjapuri
    Surjapuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in Bihar and neighboring regions, with its own distinct phonological and lexical features.
  • E. Jagdishpur
    Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
  • 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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604cc62e08190b5ba5dfc44efdc5c completed April 20, 2026, 10:49 a.m.
Created at: April 10, 2026, 1:32 p.m.