Triple
T23533057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bras Basah |
E576619
|
entity |
| Predicate | timezone |
P109
|
FINISHED |
| Object | Asia/Singapore |
—
|
NE NERFINISHED |
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: Asia/Singapore | Statement: [Bras Basah, timezone, Asia/Singapore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Singapore Context triple: [Bras Basah, timezone, Asia/Singapore]
-
A.
Singapore Standard Time
chosen
Singapore Standard Time is the time zone used throughout Singapore, corresponding to UTC+8 with no daylight saving time.
-
B.
Asia/Vladivostok
Asia/Vladivostok is the time zone covering Russia’s Far Eastern city of Vladivostok and surrounding Primorsky Krai, typically observed as UTC+10.
-
C.
Asia/Aden
Asia/Aden is an IANA time zone identifier representing the standard time observed in Aden, Yemen, within the Asia region.
-
D.
UTC+8
UTC+8 is a time zone eight hours ahead of Coordinated Universal Time, commonly used in regions such as China, Western Australia, parts of Southeast Asia, and central Indonesia.
-
E.
Brunei Darussalam Time
Brunei Darussalam Time is the standard time zone used throughout Brunei, set at UTC+8 with no daylight saving time.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac79800081908907bce55b9c68cf |
completed | April 29, 2026, 7 a.m. |
Created at: April 17, 2026, 6:10 p.m.