Triple
T23247242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forchtenberg |
E581613
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | KÜN |
—
|
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: KÜN | Statement: [Forchtenberg, vehicleRegistrationCode, KÜN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KÜN Context triple: [Forchtenberg, vehicleRegistrationCode, KÜN]
-
A.
KÜN
chosen
KÜN is the vehicle registration code for the German district of Hohenlohekreis in the state of Baden-Württemberg.
-
B.
KUN
KUN is the IATA airport code for Kaunas Airport, a commercial international airport serving the city of Kaunas in Lithuania.
-
C.
Kun
Kun is an alternative name for the Cumans, a historically significant nomadic Turkic people who roamed the Eurasian steppes during the Middle Ages.
-
D.
Kun
Kun is a prominent high-altitude mountain peak in the Indian Himalayas, known as one of the major summits of the Nun-Kun massif in the Ladakh region.
-
E.
Kuenn
Kuenn is a surname most notably associated with Harvey Kuenn, an American Major League Baseball player and manager.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193f1e8448190b8420a8dc6e24576 |
completed | April 29, 2026, 5:15 a.m. |
Created at: April 17, 2026, 4:10 p.m.