Triple
T15351029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzgitter |
E367050
|
entity |
| Predicate | hasVehicleRegistrationCode |
P1173
|
FINISHED |
| Object | SZ |
E367050
|
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: SZ | Statement: [Salzgitter, hasVehicleRegistrationCode, SZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SZ Context triple: [Salzgitter, hasVehicleRegistrationCode, SZ]
-
A.
SZ
chosen
SZ is the vehicle registration code for the German city of Salzgitter in Lower Saxony.
-
B.
SZ
SZ is the official station code used to identify the Berlin U-Bahn station Seestraße.
-
C.
S/Z
S/Z is Roland Barthes’s influential structuralist analysis of Balzac’s short story “Sarrasine,” renowned for its detailed demonstration of textual codes and readerly versus writerly texts.
-
D.
SZF
SZF is the IATA airport code for Samsun-Çarşamba Airport, a regional airport serving the city of Samsun in northern Turkey.
-
E.
SZB
SZB is the IATA airport code for Sultan Abdul Aziz Shah Airport, a secondary airport serving the Kuala Lumpur area in Malaysia.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e290efc8190b22c95dcd3e5f57f |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01fd53688190939787a3d6ff3bb9 |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.