Triple
T2080023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korea Standard Time |
E45216
|
entity |
| Predicate | historicalOffset |
P5577
|
FINISHED |
| Object | UTC+08: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+08:30 | Statement: [Korea Standard Time, historicalOffset, UTC+08:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalOffset Context triple: [Korea Standard Time, historicalOffset, UTC+08:30]
-
A.
historicalOffsetChanges
Indicates that the relationship captures past changes in an offset value between entities, including when and how that offset was modified over time.
-
B.
hasHistoricalShiftTo
Indicates a change over time in which one state, condition, or configuration is replaced or transformed into another in a historically traceable way.
-
C.
hasHistoricalShiftFrom
Indicates a relationship where one state, practice, or condition has been replaced or transformed over time from another earlier state, practice, or condition.
-
D.
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.
-
E.
historicalPartitionPeriod
Indicates that an entity existed, occurred, or is relevant during a specific historical period of territorial partition.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.