Triple
T7227470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yogyakarta International Airport |
E154816
|
entity |
| Predicate | timezoneUTCOffset |
P10251
|
FINISHED |
| Object | UTC+7 |
—
|
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 | Statement: [Yogyakarta International Airport, timezoneUTCOffset, UTC+7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneUTCOffset Context triple: [Yogyakarta International Airport, timezoneUTCOffset, UTC+7]
-
A.
utcOffsetDescription
Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
-
B.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
C.
usesUTCOffset
chosen
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
D.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
E.
timezoneBasis
Indicates that one timezone is defined, measured, or interpreted in reference to another timezone as its underlying standard or point of comparison.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9df72cc81908d1c04e6e310fbb4 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.