Triple

T22408537
Position Surface form Disambiguated ID Type / Status
Subject Havelock Town E553937 entity
Predicate locatedNear P294 FINISHED
Object Kirulapone 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: Kirulapone | Statement: [Havelock Town, locatedNear, Kirulapone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kirulapone
Context triple: [Havelock Town, locatedNear, Kirulapone]
  • A. Kirulapone chosen
    Kirulapone is a residential and commercial suburb of Colombo, Sri Lanka, known for its mixed urban character and proximity to the city center.
  • B. Kasauli
    Kasauli is a small, picturesque hill station in the Indian state of Himachal Pradesh, known for its colonial-era architecture, pine forests, and tranquil atmosphere.
  • C. Nurpur
    Nurpur is a historic town in the Kangra district of Himachal Pradesh, India, known for its ancient fort and temples amid scenic Himalayan foothills.
  • D. Nishapuri
    Nishapuri refers to the Iranian-origin Nishapurid dynasty from which the Nawabs of Awadh claimed descent.
  • E. Nalapani
    Nalapani is a historic hilltop area near Dehradun in present-day Uttarakhand, India, known for its fortified position and association with early 19th-century Anglo-Nepalese conflict.
  • 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_69e11e4e6ce8819085a1e06d886bf21c completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158badc008190a3f5afb520a25e5f completed April 29, 2026, 1:02 a.m.
Created at: April 16, 2026, 8:46 p.m.