Triple

T9083532
Position Surface form Disambiguated ID Type / Status
Subject Visakhapatnam district E217692 entity
Predicate hasTown P847 FINISHED
Object Bheemunipatnam E416086 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: Bheemunipatnam | Statement: [Visakhapatnam district, hasTown, Bheemunipatnam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bheemunipatnam
Context triple: [Visakhapatnam district, hasTown, Bheemunipatnam]
  • A. Bheemunipatnam chosen
    Bheemunipatnam is a historic coastal town in Andhra Pradesh, India, known for its former Dutch colonial presence, old fortifications, and scenic beaches along the Bay of Bengal.
  • B. Negapatam
    Negapatam is the former colonial-era name of Nagapattinam, a historic port town on the southeastern coast of India in the state of Tamil Nadu.
  • C. Rajahmundry
    Rajahmundry is a historic city in the Indian state of Andhra Pradesh, known as a major cultural and commercial center in the Godavari region.
  • D. Gannavaram
    Gannavaram is a suburban town near Vijayawada in Andhra Pradesh, India, known primarily for hosting the city's main airport.
  • E. Machilipatnam
    Machilipatnam is a coastal city in the Indian state of Andhra Pradesh, historically known as a significant port and trading center on the Bay of Bengal.
  • 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_69ca83d7a0388190ba1af89ed7ba36f9 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc960b45fc8190adf4bdc41b103e86 completed April 1, 2026, 3:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69d04781c4d08190b91d02fa43fa57e0 completed April 3, 2026, 11:04 p.m.
Created at: March 30, 2026, 7:13 p.m.