Triple
T15693974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alta Airport |
E380406
|
entity |
| Predicate | UTC offset in summer |
P713
|
FINISHED |
| Object | +02:00 |
—
|
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: +02:00 | Statement: [Alta Airport, UTC offset in summer, +02:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UTC offset in summer Context triple: [Alta Airport, UTC offset in summer, +02:00]
-
A.
summerUtcOffset
Indicates the difference in hours or minutes between local time and Coordinated Universal Time (UTC) during the summer or daylight saving period.
-
B.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
C.
differenceFromLondonTimeInSummer
Indicates the time difference between a given location and London during the summer (daylight saving) period.
-
D.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
E.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:44 a.m.