Triple

T13520257
Position Surface form Disambiguated ID Type / Status
Subject Vengurla Beach E322874 entity
Predicate near P350 FINISHED
Object Vengurla town E316878 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: Vengurla town | Statement: [Vengurla Beach, near, Vengurla town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vengurla town
Context triple: [Vengurla Beach, near, Vengurla town]
  • A. Vengurla chosen
    Vengurla is a coastal town in Maharashtra, India, known for its scenic beaches, historic forts, and cashew plantations.
  • B. Khandala
    Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
  • C. Shelkar town
    Shelkar town is a settlement in Tibet that serves as an important local center within Tingri County, known historically as a stop along routes to Mount Everest and other Himalayan regions.
  • D. Vithalwadi
    Vithalwadi is a suburban railway station in the Mumbai metropolitan area that serves local commuters on the Central Line.
  • E. Lakkundi
    Lakkundi is a historic village in Karnataka, India, renowned for its intricately carved medieval temples and stepwells built during the Western Chalukya period.
  • 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_69d80766a21881909f21a1b7421d3b8a completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbafa3df0c8190804174695587f0ea completed April 12, 2026, 2:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75d93a2608190a3a693bf4086a010 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:44 p.m.