Triple
T7496484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bremerhaven |
E177141
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | HB |
E373926
|
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: HB | Statement: [Bremerhaven, vehicleRegistrationCode, HB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HB Context triple: [Bremerhaven, vehicleRegistrationCode, HB]
-
A.
HB
HB is the second-generation Holden Torana small family car series produced in the late 1960s, known for introducing more modern styling and engineering updates over its predecessor.
-
B.
HB
chosen
HB is the official vehicle registration code used on license plates for the German city-state of Bremen.
-
C.
BH
BH is the UK postcode area covering Bournemouth and surrounding parts of southern England.
-
D.
BH
BH is a major Brazilian city and the capital of the state of Minas Gerais, known for its modernist architecture, surrounding mountains, and vibrant cultural and culinary scenes.
-
E.
BH
BH is a German vehicle registration code formerly used for the district of Ortenaukreis in the state of Baden-Württemberg.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f57c86948190aa8ee765bd497850 |
completed | March 27, 2026, 9:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c83c8686cc8190bb1f7b09cdbebcf7 |
completed | March 28, 2026, 8:39 p.m. |
Created at: March 27, 2026, 3:43 p.m.