Triple

T236955
Position Surface form Disambiguated ID Type / Status
Subject Assam E4843 entity
Predicate timeZone P109 FINISHED
Object Indian Standard Time E5066 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: Indian Standard Time | Statement: [Assam, timeZone, Indian Standard Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Indian Standard Time
Context triple: [Assam, timeZone, Indian Standard Time]
  • A. Indian Standard Time chosen
    Indian Standard Time is the time zone used throughout India, set at UTC+5:30.
  • B. Gulf Standard Time
    Gulf Standard Time is the time zone used by several Gulf countries, including the United Arab Emirates, which is four hours ahead of Coordinated Universal Time (UTC+4) and does not observe daylight saving time.
  • C. New Zealand Standard Time
    New Zealand Standard Time is the standard time zone observed in New Zealand, typically 12 hours ahead of Coordinated Universal Time (UTC+12).
  • D. China Standard Time
    China Standard Time is the single official time zone used throughout mainland China, corresponding to UTC+8.
  • E. New Zealand Daylight Time
    New Zealand Daylight Time is the daylight saving time zone used in New Zealand, typically observed during the Southern Hemisphere summer months.
  • 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_69a257c3d0708190b0871c4269d273e6 completed Feb. 28, 2026, 2:49 a.m.
NER Named-entity recognition batch_69a25ccc5d548190b505bf1d99db41bd completed Feb. 28, 2026, 3:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69a3695ec8cc8190a070462cd0022f6a completed Feb. 28, 2026, 10:17 p.m.
Created at: Feb. 28, 2026, 2:53 a.m.