Triple

T18708082
Position Surface form Disambiguated ID Type / Status
Subject Kleve district E457425 entity
Predicate hasVehicleRegistrationCode P1173 FINISHED
Object KLE 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: KLE | Statement: [Kleve district, hasVehicleRegistrationCode, KLE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KLE
Context triple: [Kleve district, hasVehicleRegistrationCode, KLE]
  • A. KLE chosen
    KLE is the vehicle registration code for the district of Cleves (Kleve) in the German state of North Rhine-Westphalia.
  • B. KLEW
    KLEW is the ICAO airport code for Auburn/Lewiston Municipal Airport in Maine, United States.
  • C. KLS
    KLS is a research center at Kiel University focused on interdisciplinary life science studies, including molecular biology, medicine, and environmental sciences.
  • D. KLS
    KLS is the IATA airport code for Southwest Washington Regional Airport, a public airport serving the Longview–Kelso area in Washington State, USA.
  • E. KOLE
    KOLE is the ICAO airport code assigned to Cattaraugus County-Olean Airport in New York, United States.
  • 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_69d8d392aad081909fe31aa03e6e97d1 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56719383481909d68c9e873ca0800 completed April 19, 2026, 11:36 p.m.
Created at: April 10, 2026, 11:50 a.m.