Triple

T11589155
Position Surface form Disambiguated ID Type / Status
Subject Kurla E274832 entity
Predicate adjacentTo 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: [Kurla, adjacentTo, Bandra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bandra
Context triple: [Kurla, adjacentTo, 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_69d6aae6b14c81908dc5a74bad7591f9 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d89463360c8190b91228c46bfe2e5f completed April 10, 2026, 6:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69f75462fe9081908b939a1c6bdba6b9 completed May 3, 2026, 1:57 p.m.
Created at: April 8, 2026, 9:38 p.m.