Triple
T21414229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Szczecin-Goleniów Airport |
E528257
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | SZZ |
—
|
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: SZZ | Statement: [Szczecin-Goleniów Airport, IATA code, SZZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SZZ Context triple: [Szczecin-Goleniów Airport, IATA code, SZZ]
-
A.
SZZ
chosen
SZZ is the three-letter IATA airport code for Szczecin-Goleniów Airport in northwestern Poland.
-
B.
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.
-
C.
ZSSS
ZSSS is the ICAO airport code for Shanghai Hongqiao International Airport, a major domestic and regional aviation hub in Shanghai, China.
-
D.
SZ
SZ is the official station code used to identify the Berlin U-Bahn station Seestraße.
-
E.
SZ
SZ is the official abbreviation for the Swiss canton of Schwyz, one of the founding cantons of Switzerland.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2032fe48190907b282e2fffa2bd |
completed | April 22, 2026, 11:33 a.m. |
Created at: April 16, 2026, 5:45 p.m.