Triple
T12498001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmö |
E298741
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Malmö Airport |
E363152
|
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: Malmö Airport | Statement: [Malmö, hasAirport, Malmö Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Malmö Airport Context triple: [Malmö, hasAirport, Malmö Airport]
-
A.
Malmö Airport
chosen
Malmö Airport is an international airport in southern Sweden serving the city of Malmö and the wider Øresund Region, including nearby parts of Denmark.
-
B.
Uppsala Airport
Uppsala Airport is a Swedish airfield near the city of Uppsala, primarily used for military and general aviation rather than large-scale commercial passenger traffic.
-
C.
Stockholm Bromma Airport
Stockholm Bromma Airport is a regional airport near central Stockholm, Sweden, primarily serving domestic and short-haul European flights.
-
D.
Gothenburg Landvetter Airport
Gothenburg Landvetter Airport is the main international airport serving the Gothenburg region in western Sweden.
-
E.
Gothenburg City Airport
Gothenburg City Airport is a regional airport serving the Gothenburg area in western Sweden.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94dfa98348190b9ac164ecdada6fe |
completed | April 10, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f64baf73188190af29b57f8ae9253f |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.