Triple

T19018970
Position Surface form Disambiguated ID Type / Status
Subject Bijwasan E465430 entity
Predicate hasNeighbourhood P4813 FINISHED
Object Kapasheda 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: Kapasheda | Statement: [Bijwasan, hasNeighbourhood, Kapasheda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kapasheda
Context triple: [Bijwasan, hasNeighbourhood, Kapasheda]
  • A. Kapashera chosen
    Kapashera is a locality in the South West district of Delhi, India, known for its proximity to the Delhi-Gurugram border and its role as an administrative and commercial hub in the area.
  • B. Khanke
    Khanke is a village in northern Iraq’s Kurdistan Region, known for hosting large camps for internally displaced Yazidis who fled ISIS violence.
  • C. Buhera
    Buhera is a rural town and district center in eastern Zimbabwe known for its agricultural activities and location within Manicaland Province.
  • D. Kabaena
    Kabaena is an island in Indonesia known for its location off the coast of Sulawesi and its mix of coastal and hilly landscapes.
  • E. Sogakope
    Sogakope is a town in southeastern Ghana known for its location along the lower Volta River and its role as a local commercial and transportation hub.
  • 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.