Triple
T9223333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schelklingen |
E221616
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | UL |
E60877
|
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: UL | Statement: [Schelklingen, vehicleRegistrationCode, UL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UL Context triple: [Schelklingen, vehicleRegistrationCode, UL]
-
A.
UL
chosen
UL is the vehicle registration code used on license plates for the city of Ulm in Germany.
-
B.
UL
UL is the two-letter IATA airline designator assigned to SriLankan Airlines, the flag carrier of Sri Lanka.
-
C.
UL
UL is the New York Stock Exchange ticker symbol for Unilever, a major multinational consumer goods company known for its food, personal care, and household products.
-
D.
LU
LU is the vehicle registration code for the German city of Ludwigshafen am Rhein in the state of Rhineland-Palatinate.
-
E.
LU
LU is the two-letter ISO 3166-1 alpha-2 country code assigned to Luxembourg for international identification and data standards.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda7903208190b4e29a1591aab78a |
completed | April 1, 2026, 8:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0664565748190a45cf382fca72cbe |
completed | April 4, 2026, 1:15 a.m. |
Created at: March 30, 2026, 7:28 p.m.