Triple
T8848382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naumburg |
E210567
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | BLK |
E189699
|
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: BLK | Statement: [Naumburg, vehicleRegistrationCode, BLK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BLK Context triple: [Naumburg, vehicleRegistrationCode, BLK]
-
A.
BLK
chosen
BLK is the vehicle registration code used on license plates for the Burgenlandkreis district in the German state of Saxony-Anhalt.
-
B.
BLK
BLK is the three-letter IATA airport code assigned to Blackpool Airport in Lancashire, England.
-
C.
Balck
Balck is a German surname most notably associated with Hermann Balck, a prominent Wehrmacht general during World War II.
-
D.
BLQ
BLQ is the three-letter IATA airport code for Bologna Guglielmo Marconi Airport, serving the city of Bologna in northern Italy.
-
E.
BLC
BLC is the commonly used abbreviation for the Boston Landmarks Commission, the city agency responsible for identifying and protecting Boston’s historic buildings and districts.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf89bd3ef48190a6a2efff18db4dbd |
completed | April 3, 2026, 9:34 a.m. |
Created at: March 30, 2026, 6:49 p.m.