Triple
T13263891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lošinj Airport |
E315866
|
entity |
| Predicate | pushpinLabel |
P9248
|
FINISHED |
| Object | LSZ |
E1030824
|
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: LSZ | Statement: [Lošinj Airport, pushpinLabel, LSZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LSZ Context triple: [Lošinj Airport, pushpinLabel, LSZ]
-
A.
LSZ
chosen
LSZ is the IATA airport code for Lošinj Airport, a small regional airport serving the island of Lošinj in Croatia.
-
B.
LSZB
LSZB is the ICAO airport code for Bern Airport, the primary airport serving Switzerland’s capital city.
-
C.
LSZ reduction formula
The LSZ reduction formula is a key result in quantum field theory that relates time-ordered correlation functions of fields to observable scattering amplitudes in the S-matrix.
-
D.
LZ
LZ is the IATA airline designator historically assigned to the former Bulgarian flag carrier Balkan Bulgarian Airlines.
-
E.
LZ
LZ is the vehicle registration code assigned to the municipality of Kals am Großglockner in Austria.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9901c65048190bd8b3c4872f22520 |
completed | April 11, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716cac5388190a839ec1dbdcdbf82 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:25 p.m.