Triple

T12239888
Position Surface form Disambiguated ID Type / Status
Subject Andheri E291700 entity
Predicate hasArea P175 FINISHED
Object Versova E275880 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: Versova | Statement: [Andheri, hasArea, Versova]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Versova
Context triple: [Andheri, hasArea, Versova]
  • A. Versova chosen
    Versova is a coastal neighborhood in Mumbai, India, known for its beach, fishing village, and role as a key residential and commercial hub in the city.
  • B. Malaya Nevka
    Malaya Nevka is a distributary channel of the Neva River in Saint Petersburg, Russia, forming part of the city’s intricate river and canal network.
  • C. Охта
    Охта — это река на северо-западе России, протекающая через Санкт-Петербург и впадающая в Неву.
  • D. Vyatskoye
    Vyatskoye is a rural locality in Russia’s Khabarovsk Krai, historically noted as the birthplace of North Korean leader Kim Jong Il.
  • E. Piotrovskaya
    Piotrovskaya is the feminine form of the Russian surname Piotrovsky, typically used for women in Russian naming conventions.
  • 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_69d6ab67950c8190be08450a06228c4b completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb45340819093365f8efdf85f75 completed April 10, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60ab3ae2481908f65d8ac61a6b2e4 completed May 2, 2026, 2:31 p.m.
Created at: April 8, 2026, 9:51 p.m.