Triple

T1410549
Position Surface form Disambiguated ID Type / Status
Subject Bombay Time E31792 entity
Predicate coexistedWith P12845 FINISHED
Object Madras Time E32695 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: Madras Time | Statement: [Bombay Time, coexistedWith, Madras Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Madras Time
Context triple: [Bombay Time, coexistedWith, Madras Time]
  • A. Madras Time chosen
    Madras Time was a former local time standard used in the Madras (now Chennai) region of India before the adoption of a unified national time zone.
  • B. Calcutta Time
    Calcutta Time was a former local time standard used in Kolkata (then Calcutta) before the adoption of a unified national time zone in India.
  • C. Bombay Time
    Bombay Time was a former local time standard used in the city of Bombay (now Mumbai) before the adoption of a unified national time across India.
  • D. Zulu time
    Zulu time is a standardized time reference used worldwide—especially in aviation, military, and navigation—corresponding to Coordinated Universal Time (UTC) and denoted by the letter "Z."
  • E. Indian Standard Time
    Indian Standard Time is the time zone used throughout India, set at UTC+5:30.
  • 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_69a49918e1f88190ba610f9dc8114578 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c3e0bfd08190a50820bc7585c28f completed March 1, 2026, 10:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69ace57be14881908d469d2b5333d6d5 completed March 8, 2026, 2:57 a.m.
Created at: March 1, 2026, 7:59 p.m.