Triple

T22886691
Position Surface form Disambiguated ID Type / Status
Subject Dambadeniya E567621 entity
Predicate near P350 FINISHED
Object Kurunegala 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: Kurunegala | Statement: [Dambadeniya, near, Kurunegala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kurunegala
Context triple: [Dambadeniya, near, Kurunegala]
  • A. Kurunegala chosen
    Kurunegala is a major city in Sri Lanka’s North Western Province, serving as an important commercial and transport hub with historical and political significance.
  • B. Anuradhapura
    Anuradhapura is an ancient city in Sri Lanka renowned as a former capital and a major center of early Theravada Buddhism.
  • C. Kegalle
    Kegalle is a major town in central Sri Lanka known for its rubber plantations and proximity to the Pinnawala Elephant Orphanage.
  • D. Dambulla
    Dambulla is a historic town in Sri Lanka best known for its UNESCO-listed cave temple complex featuring ancient Buddhist murals and statues.
  • E. Peradeniya
    Peradeniya is a town in central Sri Lanka renowned for its historic university and expansive Royal Botanical Gardens.
  • 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_69e2458a92ec81908fc1cd5f6407d2ab completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17fc1e3408190833a062afbea509d completed April 29, 2026, 3:49 a.m.
Created at: April 17, 2026, 3:40 p.m.