Triple

T18212788
Position Surface form Disambiguated ID Type / Status
Subject Vyšné Hágy E436074 entity
Predicate hasCountryCode P189 FINISHED
Object SK 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: SK | Statement: [Vyšné Hágy, hasCountryCode, SK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SK
Context triple: [Vyšné Hágy, hasCountryCode, SK]
  • A. SK
    SK is the IATA airline designator used worldwide to identify Scandinavian Airlines on tickets, timetables, and flight information systems.
  • B. SK chosen
    SK is the ISO 3166-1 alpha-2 country code for Slovakia, a landlocked Central European nation known for its mountains, castles, and membership in the European Union.
  • C. SK
    SK is the vehicle registration code used for motor vehicles registered in the town of Šakiai in Lithuania.
  • D. SK
    SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
  • E. SK
    SK is the vehicle registration code used on license plates for vehicles registered in Skopje, the capital city of North Macedonia.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e22a26308190a6720b41a9bbfc2d completed April 19, 2026, 2:09 p.m.
Created at: April 10, 2026, 10:32 a.m.