Triple

T17813201
Position Surface form Disambiguated ID Type / Status
Subject Krzeszowice E444765 entity
Predicate vehicleRegistrationCode P1173 FINISHED
Object KRA 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: KRA | Statement: [Krzeszowice, vehicleRegistrationCode, KRA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KRA
Context triple: [Krzeszowice, vehicleRegistrationCode, KRA]
  • A. KRA
    KRA is Kenya’s national tax collection and revenue administration agency responsible for assessing, collecting, and accounting for government revenue.
  • B. KRA chosen
    KRA is the vehicle registration code assigned to cars registered in the Kraków region of Poland, including the town of Słomniki.
  • C. KRCA
    KRCA is a Los Angeles-area television station that currently operates as a Spanish-language independent outlet serving Southern California viewers.
  • D. KRU
    KRU is a German vehicle registration code assigned to the district of Günzburg in the state of Bavaria.
  • E. Kra 1
    Kra 1 is the designated type strain of the hyperthermophilic archaeon Thermoproteus tenax, used as the reference for defining the species’ characteristics.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4887c63608190b29a407cabff0bc5 completed April 19, 2026, 7:47 a.m.
Created at: April 10, 2026, 10:14 a.m.