Triple

T21944664
Position Surface form Disambiguated ID Type / Status
Subject Versova Kabristan E541904 entity
Predicate locatedIn P40 FINISHED
Object Versova 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: Versova | Statement: [Versova Kabristan, locatedIn, Versova]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Versova
Context triple: [Versova Kabristan, locatedIn, 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. Novy Port
    Novy Port is a remote Arctic settlement and key Russian seaport on the coast of the Ob Bay, serving as an important hub for regional shipping and resource export.
  • 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_69e0c47e2e5c81909a7f74ce3de50911 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1242688988190a7b8f033c49368de completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 7:56 p.m.