Triple
T16533213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich–Nuremberg high-speed railway |
E401618
|
entity |
| Predicate | railwaySignalling |
P19148
|
FINISHED |
| Object | PZB |
E386840
|
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: PZB | Statement: [Munich–Nuremberg high-speed railway, railwaySignalling, PZB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PZB Context triple: [Munich–Nuremberg high-speed railway, railwaySignalling, PZB]
-
A.
PZB
chosen
PZB is a German train protection system that automatically supervises train speeds and signal observance to prevent accidents such as passing signals at danger.
-
B.
PZ
PZ is the Italian vehicle registration code assigned to the Province of Potenza in the Basilicata region.
-
C.
PZ
PZ is the station code for Prinzregentenplatz, a Munich U-Bahn station on the city’s rapid transit network.
-
D.
PZ
PZ is the vehicle registration code used on license plates for vehicles registered in the Preveza regional unit of Greece.
-
E.
PZ
PZ is the IATA airline designator assigned to LATAM Airlines Paraguay, the Paraguayan branch of the LATAM Airlines Group.
- 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.