Triple
T1647182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malaysia Time |
E35608
|
entity |
| Predicate | previousStandardTimeBeforeUnification |
P5577
|
FINISHED |
| Object | UTC+7:30 |
—
|
LITERAL 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: UTC+7:30 | Statement: [Malaysia Time, previousStandardTimeBeforeUnification, UTC+7:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStandardTimeBeforeUnification Context triple: [Malaysia Time, previousStandardTimeBeforeUnification, UTC+7:30]
-
A.
observedAsStandardTimeIn
Indicates that a particular time standard is used as the official or standard time within a specified place or region.
-
B.
previousUTCOffset
chosen
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
C.
laterStandardization
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
D.
timePeriodOfStandardization
Indicates the time span during which a particular standard was formally established or in effect.
-
E.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
- F. None of above.
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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.