Triple

T11518242
Position Surface form Disambiguated ID Type / Status
Subject Landsberg E273086 entity
Predicate vehicleRegistrationCode P1173 FINISHED
Object SK E66662 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: SK | Statement: [Landsberg, vehicleRegistrationCode, SK]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SK
Context triple: [Landsberg, vehicleRegistrationCode, SK]
  • A. SK
    SK is the IATA airline designator used worldwide to identify Scandinavian Airlines on tickets, timetables, and flight information systems.
  • B. SK
    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 chosen
    SK is the postcode area covering Stockport and surrounding parts of Greater Manchester and nearby counties in North West England.
  • D. SK
    SK is the official vehicle registration code assigned to the Indian state of Sikkim.
  • E. SK
    SK is the archaeological site code for Swartkrans, a significant South African paleoanthropological cave site known for its early hominin fossils and stone tools.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d87fcf927081908ef89eff7ad833b0 completed April 10, 2026, 4:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69e62530a6b08190a8ba3c410e79cf72 completed April 20, 2026, 1:08 p.m.
Created at: April 8, 2026, 9:36 p.m.