Triple
T16184787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghanistan–China border |
E392771
|
entity |
| Predicate | timeZoneOnChineseSide |
P122052
|
FINISHED |
| Object | UTC+8 |
—
|
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+8 | Statement: [Afghanistan–China border, timeZoneOnChineseSide, UTC+8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneOnChineseSide Context triple: [Afghanistan–China border, timeZoneOnChineseSide, UTC+8]
-
A.
timeZoneDeJureChina
Indicates the official or legally designated time zone that applies within the jurisdiction of China.
-
B.
timeZoneOnUSSide
Indicates that the referenced time zone is the one used on the United States side of a border, region, or cross-national context.
-
C.
differenceFromChinaStandardTime
Indicates the time offset or deviation of something’s time setting relative to China Standard Time.
-
D.
linkedToMainlandTimeZone
Indicates that an entity’s time zone is synchronized with or derived from the primary mainland time zone of a region or country.
-
E.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
- F. None of above. chosen
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22060dcf88190b7c662946a5f0191 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.