Triple
T4562152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steinheim am Albuch |
E121816
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | HDH |
E111221
|
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: HDH | Statement: [Steinheim am Albuch, vehicleRegistrationCode, HDH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HDH Context triple: [Steinheim am Albuch, vehicleRegistrationCode, HDH]
-
A.
HDH
chosen
HDH is the vehicle registration code used on license plates for the German town of Heidenheim an der Brenz.
-
B.
DH
DH is the commonly used currency symbol representing the Moroccan dirham.
-
C.
DH
DH is the postcode area covering Durham and surrounding parts of North East England in the United Kingdom.
-
D.
DH
DH is the official abbreviation for Puerto Rico’s Department of Treasury, the government agency responsible for managing the island’s fiscal and tax affairs.
-
E.
DHR
DHR is the stock ticker symbol for Danaher Corporation, a global science and technology company focused on life sciences, diagnostics, and environmental and applied solutions.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd582f21648190b49284eb61b618c9 |
completed | March 20, 2026, 2:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdc59b2514819091f3845307cb1c8b |
completed | March 20, 2026, 10:09 p.m. |
Created at: March 20, 2026, 1:09 p.m.