Triple

T4730574
Position Surface form Disambiguated ID Type / Status
Subject Uva Province E104995 entity
Predicate timeZone P109 FINISHED
Object Sri Lanka Standard Time E67156 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: Sri Lanka Standard Time | Statement: [Uva Province, timeZone, Sri Lanka Standard Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sri Lanka Standard Time
Context triple: [Uva Province, timeZone, Sri Lanka Standard Time]
  • A. Sri Lanka Standard Time chosen
    Sri Lanka Standard Time is the time zone used throughout Sri Lanka, set at UTC+5:30.
  • B. Myanmar Standard Time
    Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no daylight saving time.
  • C. Bangladesh Standard Time
    Bangladesh Standard Time is the time zone used in Bangladesh, corresponding to UTC+6 hours with no daylight saving time.
  • D. Mauritius Time
    Mauritius Time is the standard time zone used throughout the island nation of Mauritius in the Indian Ocean.
  • E. Jamaica Standard Time
    Jamaica Standard Time is the time zone observed throughout Jamaica, corresponding to UTC−5 without daylight saving time.
  • 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_69bd43ee52048190b81a4f066534ffb3 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64629bc081908754aa8a2630091f completed March 20, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10a9386c81908557fe4feb190e8a completed March 21, 2026, 3:29 a.m.
Created at: March 20, 2026, 1:19 p.m.