Triple

T19628536
Position Surface form Disambiguated ID Type / Status
Subject Kuragala archaeological site E471201 entity
Predicate near P350 FINISHED
Object Balangoda town 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: Balangoda town | Statement: [Kuragala archaeological site, near, Balangoda town]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balangoda town
Context triple: [Kuragala archaeological site, near, Balangoda town]
  • A. Balangoda chosen
    Balangoda is a town in south-central Sri Lanka known for its archaeological significance and as a regional commercial center in the Sabaragamuwa Province.
  • B. Peliyagoda
    Peliyagoda is a suburban town in Sri Lanka located just northeast of Colombo, known for its transport links and commercial activity.
  • C. Ambalangoda
    Ambalangoda is a coastal town in southwestern Sri Lanka known for its traditional mask carving and puppet arts.
  • D. Koggala
    Koggala is a coastal town in southern Sri Lanka known for its scenic beach, lagoon, and proximity to the historic city of Galle.
  • E. Pallamallawa
    Pallamallawa is a small rural village in northern New South Wales, Australia, known for its agricultural surroundings and close-knit community.
  • 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_69d8e511f28481909f4bc3ea9191e54a completed April 10, 2026, 11:54 a.m.
NER Named-entity recognition batch_69e641007e5881908da78e50aa36f340 completed April 20, 2026, 3:06 p.m.
Created at: April 10, 2026, 1:44 p.m.