Triple

T10752697
Position Surface form Disambiguated ID Type / Status
Subject Singapore Changi Airport E253611 entity
Predicate IATAcode P418 FINISHED
Object SIN E418863 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: SIN | Statement: [Singapore Changi Airport, IATAcode, SIN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SIN
Context triple: [Singapore Changi Airport, IATAcode, SIN]
  • A. SIN chosen
    SIN is the IATA airport code for Singapore Changi Airport, the main international gateway to Singapore and one of the world’s busiest and most acclaimed airports.
  • B. Sines
    Sines is a coastal town in Portugal known as the birthplace of the famed explorer Vasco da Gama.
  • C. Sinn
    Sinn is a river in northern Bavaria, Germany, that flows through the Lower Franconia region.
  • D. SANG
    SANG is the acronym for the Saudi Arabian National Guard, a key military and security force responsible for protecting the Saudi royal family, strategic facilities, and internal stability.
  • E. SON
    SON is the commonly used acronym for the Saugeen Ojibway Nation, an Indigenous community in Ontario composed primarily of the Saugeen First Nation and the Chippewas of Nawash Unceded First Nation.
  • 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_69d6aa5e51e8819095f06881cecf152e completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d71dc184d0819085f8bc4edb034377 completed April 9, 2026, 3:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69dbdb897f7c81909002f2478613eff8 completed April 12, 2026, 5:51 p.m.
Created at: April 8, 2026, 9:15 p.m.