Triple

T4688739
Position Surface form Disambiguated ID Type / Status
Subject Stockholm Arlanda Airport E103982 entity
Predicate IATA code P2569 FINISHED
Object ARN E103982 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: ARN | Statement: [Stockholm Arlanda Airport, IATA code, ARN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ARN
Context triple: [Stockholm Arlanda Airport, IATA code, 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. AN
    AN is the vehicle registration code used on license plates for the Ansbach district in the Middle Franconia region of Bavaria, Germany.
  • C. AN
    AN is the standard abbreviation for Anthropology News, a publication focused on current developments, research, and issues in the field of anthropology.
  • D. AN
    AN is the abbreviation commonly used for the National Alliance, a political organization.
  • E. AN
    AN is the former ISO 3166-1 alpha-2 country code assigned to the now-dissolved Caribbean territory of the Netherlands Antilles.
  • 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_69bd43df91f481908e9add1b617b60ef completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd6399621881909aa8ffb1c27284e9 completed March 20, 2026, 3:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69be03b75e3481908aa27eeaeec490ca completed March 21, 2026, 2:34 a.m.
Created at: March 20, 2026, 1:16 p.m.