Triple

T3896769
Position Surface form Disambiguated ID Type / Status
Subject South East Asia Command E90388 entity
Predicate garrison P75 FINISHED
Object Kandy E94221 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: Kandy | Statement: [South East Asia Command, garrison, Kandy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kandy
Context triple: [South East Asia Command, garrison, Kandy]
  • A. Kandy chosen
    Kandy is a historic city in central Sri Lanka renowned for its cultural heritage, including the Temple of the Tooth and its role as a former royal stronghold.
  • B. Badulla
    Badulla is a major town in Sri Lanka’s central highlands, known as the capital of Uva Province and a regional hub surrounded by tea plantations and scenic mountain landscapes.
  • C. Ratnapura
    Ratnapura is a major city in Sri Lanka renowned as the country’s primary gem-mining and trading center.
  • D. Nuwara Eliya
    Nuwara Eliya is a Sri Lankan highland city famed for its cool climate, tea plantations, and colonial-era architecture.
  • E. Galle
    Galle is a historic coastal city in southern Sri Lanka renowned for its well-preserved colonial-era fort and long-standing role as a key Indian Ocean trading hub.
  • 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_69aed95d315881908cbf1bf4a7215fbf completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeecd34e608190bf1ca1d0c04562b2 completed March 9, 2026, 3:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69b562821c3c81909805cb877288405b completed March 14, 2026, 1:28 p.m.
Created at: March 9, 2026, 3:21 p.m.