Triple

T15679810
Position Surface form Disambiguated ID Type / Status
Subject Damascus International Airport E377539 entity
Predicate IATA code P2569 FINISHED
Object DAM E377539 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: DAM | Statement: [Damascus International Airport, IATA code, DAM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DAM
Context triple: [Damascus International Airport, IATA code, DAM]
  • A. DAM chosen
    DAM is the three-letter IATA airport code for Damascus International Airport, the main airport serving Syria’s capital city.
  • B. DAM
    DAM is the National Rail station code used to identify Dalmeny railway station in Scotland’s rail network.
  • C. DAM
    DAM is a Frankfurt-based museum dedicated to the history, theory, and contemporary practice of architecture in Germany and beyond.
  • D. DPM
    DPM is the abbreviation for the División de Policía Militar, a military police division responsible for law enforcement and security duties within a nation's armed forces.
  • E. DIT
    DIT is the South Australian government department responsible for planning, developing, and managing the state’s transport systems and infrastructure.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f2f1640819086efd5a73bb9734a completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6ee2a33c81908fcd120ca670b309 completed May 9, 2026, 5:29 p.m.
Created at: April 10, 2026, 4:16 a.m.