Triple

T2797432
Position Surface form Disambiguated ID Type / Status
Subject Lanseria International Airport E53071 entity
Predicate UTC offset P34679 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: [Lanseria International Airport, UTC offset, +02:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UTC offset
Context triple: [Lanseria International Airport, UTC offset, +02:00]
  • A. utcOffsetDescription chosen
    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. UTCoffsetComparison
    Indicates a comparison between the time zone UTC offsets of two entities, specifying how their local times differ relative to Coordinated Universal Time.
  • D. UTCOffsetStandardTime
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • E. timeOffsetReference
    Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
  • 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_69ab495a90788190941b6917e1eca3a6 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abddf0f4988190bffc3abab7edbb81 completed March 7, 2026, 8:12 a.m.
PD Predicate disambiguation batch_69abdd040f9481908e9c7a2df88ea1ae completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:58 p.m.