Triple

T6986881
Position Surface form Disambiguated ID Type / Status
Subject Tianjin Binhai International Airport E161985 entity
Predicate timezone P109 FINISHED
Object China Standard Time E5773 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: China Standard Time | Statement: [Tianjin Binhai International Airport, timezone, China Standard Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: China Standard Time
Context triple: [Tianjin Binhai International Airport, timezone, China Standard Time]
  • A. China Standard Time chosen
    China Standard Time is the single official time zone used throughout mainland China, corresponding to UTC+8.
  • B. Korea Standard Time
    Korea Standard Time is the time zone used on the Korean Peninsula, set at UTC+9 hours.
  • C. Singapore Standard Time
    Singapore Standard Time is the time zone used throughout Singapore, corresponding to UTC+8 with no daylight saving time.
  • D. Indochina Time
    Indochina Time is the standard time zone (UTC+7) used in several Southeast Asian countries, including Thailand, Vietnam, Cambodia, and Laos.
  • E. Myanmar Standard Time
    Myanmar Standard Time is the time zone used throughout Myanmar, set at UTC+6:30 with no 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_69c68856d7808190ab33ee914640281b completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6db95c6148190bdb5f355ac04db3f completed March 27, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c761cfda14819088e11889f0151a37 completed March 28, 2026, 5:06 a.m.
Created at: March 27, 2026, 2:32 p.m.