Triple
T20959964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE 4 |
E516212
|
entity |
| Predicate | trainProtectionSystem |
P40340
|
FINISHED |
| Object | PZB |
—
|
NE NERFINISHED |
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: [ICE 4, trainProtectionSystem, PZB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PZB Context triple: [ICE 4, trainProtectionSystem, 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 commonly used abbreviation for Peshawar Zalmi, a professional cricket franchise that competes in the Pakistan Super League.
-
E.
PZ
PZ is the vehicle registration code used on license plates for vehicles registered in the Preveza regional unit of Greece.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6e50988190a564d2aaf1a9bc54 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 1:30 p.m.