Triple
T6374437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walsrode |
E143427
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | HK |
E163585
|
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: HK | Statement: [Walsrode, vehicleRegistrationCode, HK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HK Context triple: [Walsrode, vehicleRegistrationCode, HK]
-
A.
HK
HK is the vehicle registration code used for the Czech city of Hradec Králové.
-
B.
HK
HK is a renowned German defense manufacturer best known for designing and producing small arms such as pistols, rifles, and submachine guns used by military and law enforcement worldwide.
-
C.
HK
chosen
HK is the vehicle registration code used on license plates for vehicles registered in Ahlden, a municipality in Lower Saxony, Germany.
-
D.
HK
HK is the vehicle registration code used for motor vehicles registered in Heraklion, a major city on the island of Crete in Greece.
-
E.
Hong
Hong is a Chinese-origin surname shared by various notable individuals across different fields and regions.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0683ab8e08190ab3c9a5000b1d2be |
completed | March 22, 2026, 10:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d9820f08190b12754d94507228f |
completed | March 27, 2026, 7:11 a.m. |
Created at: March 22, 2026, 4:33 p.m.