Triple
T11701371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siilinjärvi |
E278131
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | KUO |
E278133
|
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: KUO | Statement: [Siilinjärvi, hasVehicleRegistrationCode, KUO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KUO Context triple: [Siilinjärvi, hasVehicleRegistrationCode, KUO]
-
A.
KUO
chosen
KUO is the IATA airport code for Kuopio Airport in Finland.
-
B.
Ku
Ku is a principal Hawaiian god associated with war, politics, and prosperity, widely venerated in traditional Native Hawaiian religion.
-
C.
KU2
KU2 is the stock ticker symbol for KUKA, a German industrial robotics and automation company.
-
D.
Kui
Kui is a South-Central Dravidian language spoken primarily by the Khond (Kondh) tribal communities in eastern India, especially in the state of Odisha.
-
E.
Ko
Ko is a Japanese given-name element commonly used in female names, often carrying meanings like “child” depending on the kanji used.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49a025881909377c81d3debf465 |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef834244308190b435e49371d6a6e1 |
completed | April 27, 2026, 3:39 p.m. |
Created at: April 8, 2026, 9:40 p.m.