Triple
T2963045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erlangen |
E80092
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | ER |
E97822
|
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: ER | Statement: [Erlangen, vehicleRegistrationCode, ER]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ER Context triple: [Erlangen, vehicleRegistrationCode, ER]
-
A.
ER
ER is a critically acclaimed American medical drama television series that follows the personal and professional lives of staff in a busy Chicago emergency room.
-
B.
ER
chosen
ER is the vehicle registration code assigned to the German city of Erlangen in the state of Bavaria.
-
C.
ER
ER is the commonly used abbreviation for United Russia, the dominant ruling political party in the Russian Federation.
-
D.
RE
RE is the two-letter ISO 3166-1 alpha-2 country code assigned to the French overseas department and region of Réunion.
-
E.
RE
RE is the common abbreviation for the British Army’s Corps of Royal Engineers, responsible for military engineering and technical support.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9957602c819089b673966fd619e0 |
completed | March 8, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fc98d94481908282d21394dc24a7 |
completed | March 11, 2026, 5:24 a.m. |
Created at: March 8, 2026, 2:57 p.m.