Triple
T1421271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanzarote Airport |
E30228
|
entity |
| Predicate | summerUTCoffset |
P5550
|
FINISHED |
| Object | UTC+01: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: UTC+01:00 | Statement: [Lanzarote Airport, summerUTCoffset, UTC+01:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerUTCoffset Context triple: [Lanzarote Airport, summerUTCoffset, UTC+01:00]
-
A.
summerTimeZone
chosen
Indicates that a specified region or entity uses a particular time zone during the summer or daylight-saving period.
-
B.
differenceFromLondonTimeInSummer
Indicates the time difference between a given location and London during the summer (daylight saving) period.
-
C.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
-
D.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
-
E.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c42210948190a8fb5e3f9ee3213b |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf0d64c08190ac12977b86fbe4ab |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 8 p.m.