Triple

T12141973
Position Surface form Disambiguated ID Type / Status
Subject Kościerzyna E289205 entity
Predicate vehicleRegistrationCode P1173 FINISHED
Object GKS E142549 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: GKS | Statement: [Kościerzyna, vehicleRegistrationCode, GKS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GKS
Context triple: [Kościerzyna, vehicleRegistrationCode, GKS]
  • A. GKS chosen
    GKS is a Polish vehicle registration code assigned to the Słupsk area in the Pomeranian Voivodeship.
  • B. GCK
    GCK is the three-letter IATA airport code for Garden City Regional Airport in Garden City, Kansas, United States.
  • C. GKO
    GKO was the supreme emergency governing body of the Soviet Union during World War II, overseeing the country’s military, economic, and political mobilization for the war effort.
  • D. GDK
    GDK is the low-level drawing and windowing system library that underpins GTK, providing an abstraction layer over the underlying graphical system.
  • E. CGK
    CGK is the IATA airport code for Soekarno–Hatta International Airport, the main international gateway serving Jakarta, Indonesia.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915a9838081909622cc14df2a2582 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f5f692ee048190ab42c92296fd28fb completed May 2, 2026, 1:05 p.m.
Created at: April 8, 2026, 9:49 p.m.