Triple

T21965264
Position Surface form Disambiguated ID Type / Status
Subject Terminal 3 (Stockholm Arlanda Airport) E542440 entity
Predicate hasIATACodeOfAirport P2569 FINISHED
Object ARN 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: ARN | Statement: [Terminal 3 (Stockholm Arlanda Airport), hasIATACodeOfAirport, ARN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARN
Context triple: [Terminal 3 (Stockholm Arlanda Airport), hasIATACodeOfAirport, ARN]
  • A. ARN chosen
    ARN is the three-letter IATA airport code for Stockholm Arlanda Airport, the main international gateway to Stockholm and one of Sweden’s busiest airports.
  • B. ARN
    ARN is the three-letter National Rail station code assigned to Arnside railway station in Cumbria, England.
  • C. Arn
    Arn is the station code for Arnemuiden railway station in the Netherlands.
  • D. ARAM
    ARAM is a fast-paced League of Legends game mode where teams fight continuously on a single narrow bridge-like map with randomly assigned champions.
  • E. ANK
    ANK is a German vehicle registration code used for the district of Vorpommern-Greifswald in the state of Mecklenburg-Vorpommern.
  • 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1245aabf88190a44564e6eaaa94ce completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.