Triple

T12001406
Position Surface form Disambiguated ID Type / Status
Subject Kotka E285670 entity
Predicate locatedInTimeZone P109 FINISHED
Object EET E29392 NE 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: EET | Statement: [Kotka, locatedInTimeZone, EET]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EET
Context triple: [Kotka, locatedInTimeZone, EET]
  • A. EET chosen
    EET is a time zone used in parts of Eastern Europe and the Eastern Mediterranean, typically two hours ahead of Coordinated Universal Time (UTC+2).
  • B. EETN
    EETN is the ICAO airport code for Lennart Meri Tallinn Airport, the main international airport serving Tallinn, Estonia.
  • C. EGTE
    EGTE is the ICAO airport code for Exeter Airport, a regional airport serving Exeter and the surrounding area in Devon, England.
  • D. EIT
    EIT is a European Union body that fosters innovation, entrepreneurship, and education by integrating business, research, and higher education institutions across Europe.
  • E. EE
    EE is the two-letter country code for Estonia, a Northern European nation on the Baltic Sea.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6ab45a368819084fce08bf0dc3705 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903c36b248190b446b17def94885b completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f4729eb4a081909d93b3fc74509d86 completed May 1, 2026, 9:30 a.m.
Created at: April 8, 2026, 9:46 p.m.