Triple
T13278377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höchstädt an der Donau |
E316250
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | DLG |
E316251
|
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: DLG | Statement: [Höchstädt an der Donau, vehicleRegistrationCode, DLG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DLG Context triple: [Höchstädt an der Donau, vehicleRegistrationCode, DLG]
-
A.
DLG
chosen
DLG is the vehicle registration code for the municipality of Blindheim in Germany.
-
B.
DLG-6
DLG-6 was the hull classification for USS Farragut, a U.S. Navy guided missile frigate later reclassified as a guided missile destroyer and lead ship of her class during the Cold War era.
-
C.
DLJ
DLJ was the New York Stock Exchange ticker symbol for Donaldson, Lufkin & Jenrette, a prominent U.S. investment bank and securities firm.
-
D.
DLU
DLU is the vehicle registration code assigned to the city of Lubin in Poland.
-
E.
DPL
DPL is a U.S. government export control list identifying individuals and organizations prohibited from participating in export-related activities.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99043fba88190872ede6f63e2fbcb |
completed | April 11, 2026, 12:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716cfea308190836eb4892e7c5eb4 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:26 p.m.