Triple

T18323280
Position Surface form Disambiguated ID Type / Status
Subject Corvo Airport E438936 entity
Predicate timezone P109 FINISHED
Object Azores Time NE NERFINISHED

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: Azores Time | Statement: [Corvo Airport, timezone, Azores Time]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Azores Time
Context triple: [Corvo Airport, timezone, Azores Time]
  • A. Azores Time chosen
    Azores Time is the standard time zone used in the Azores archipelago of Portugal, typically one hour behind mainland Portuguese time.
  • B. Cape Verde Time
    Cape Verde Time is the standard time zone used throughout the island nation of Cape Verde, corresponding to UTC−01:00.
  • C. Azores Summer Time
    Azores Summer Time is the daylight saving time observed in the Azores archipelago, running one hour ahead of its standard time during the summer months.
  • D. East Greenland Time
    East Greenland Time is a time zone used in eastern Greenland that is typically several hours ahead of Coordinated Universal Time and distinct from the time observed in western Greenland.
  • E. West Greenland Time
    West Greenland Time is the standard time zone used in western Greenland, including the capital Nuuk, typically corresponding to UTC−3.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b916a2d081909e249e4902f6aad9 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50aa886508190902ffc26b30731ae completed April 19, 2026, 5:02 p.m.
Created at: April 10, 2026, 10:36 a.m.