Triple

T11443870
Position Surface form Disambiguated ID Type / Status
Subject Khar E271213 entity
Predicate borderedBy P224 FINISHED
Object Bandra E269503 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: Bandra | Statement: [Khar, borderedBy, Bandra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bandra
Context triple: [Khar, borderedBy, Bandra]
  • A. Bandra chosen
    Bandra is a prominent coastal suburb of Mumbai known for its upscale neighborhoods, vibrant nightlife, historic churches, and seaside promenades.
  • B. Andheri
    Andheri is a major residential, commercial, and transport hub in Mumbai, India, known for its busy railway station, metro connectivity, and proximity to the city’s airports and film industry areas.
  • C. Borivali
    Borivali is a suburban residential and commercial neighborhood in the northwestern part of Mumbai, India, known for its connectivity and proximity to the Sanjay Gandhi National Park.
  • D. Colaba
    Colaba is a prominent coastal neighborhood in South Mumbai known for its historic architecture, bustling markets, and major landmarks along the Arabian Sea.
  • E. Bhandup
    Bhandup is a suburban residential and industrial locality in the northeastern part of Mumbai, 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_69d6aadff8888190a13f253f0d460874 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8088a66f48190b2b4a56cd62097cf completed April 9, 2026, 8:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbaa8acc8190839b9a9f9f821168 completed May 3, 2026, 4:14 a.m.
Created at: April 8, 2026, 9:35 p.m.