Triple
T9731680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burkhardtsdorf |
E235758
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | ERZ |
E408329
|
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: ERZ | Statement: [Burkhardtsdorf, hasVehicleRegistrationCode, ERZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ERZ Context triple: [Burkhardtsdorf, hasVehicleRegistrationCode, ERZ]
-
A.
ERZ
chosen
ERZ is the vehicle registration code for the Erzgebirgskreis district in the Free State of Saxony, Germany.
-
B.
ER3
ER3 is the IATA aircraft type code used to designate the Embraer ERJ 135 regional jet.
-
C.
Er
Er is a minor biblical figure in the Book of Genesis, known as the firstborn son of Judah whose early death led to the levirate marriage of his widow Tamar.
-
D.
ER
ER is the vehicle registration code assigned to the German city of Erlangen in the state of Bavaria.
-
E.
ER
ER is the commonly used abbreviation for United Russia, the dominant ruling political party in the Russian Federation.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb2373c81909139c7a2ff2aa541 |
completed | April 1, 2026, 10:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fb97b6c81908d5f1d4f587a9188 |
completed | April 4, 2026, 11:33 p.m. |
Created at: March 30, 2026, 8:22 p.m.