Triple
T16533212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich–Nuremberg high-speed railway |
E401618
|
entity |
| Predicate | railwaySignalling |
P19148
|
FINISHED |
| Object | LZB |
E386839
|
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: LZB | Statement: [Munich–Nuremberg high-speed railway, railwaySignalling, LZB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LZB Context triple: [Munich–Nuremberg high-speed railway, railwaySignalling, LZB]
-
A.
LZB
chosen
LZB is a continuous automatic train control and cab signaling system used on high-speed and heavy-traffic railway lines, particularly in Germany and neighboring countries.
-
B.
LZ
LZ is the stock ticker symbol for The Lubrizol Corporation, a specialty chemicals company known for its lubricant additives and advanced materials.
-
C.
LZ
LZ is the IATA airline designator historically assigned to the former Bulgarian flag carrier Balkan Bulgarian Airlines.
-
D.
LZ
LZ is the vehicle registration code assigned to the municipality of Kals am Großglockner in Austria.
-
E.
LZA
LZA is the regional vehicle registration code assigned to motor vehicles registered in the city of Zamość in Poland.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed97b0881909de106418aca8180 |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006093244081909ae74674de966d6d |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:15 a.m.