Triple

T15753793
Position Surface form Disambiguated ID Type / Status
Subject Unalaska Airport E381914 entity
Predicate FAAcode P420 FINISHED
Object DUT E1175893 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: DUT | Statement: [Unalaska Airport, FAAcode, DUT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DUT
Context triple: [Unalaska Airport, FAAcode, DUT]
  • A. DUT
    DUT is a public university of technology located in Durban, South Africa, offering a range of career-focused and applied science programs.
  • B. DUT chosen
    DUT is the IATA airport code for Unalaska Airport, which serves the city of Unalaska in Alaska, United States.
  • C. DUCET
    DUCET is the Default Unicode Collation Element Table, a standard reference used to define the sorting and comparison order of Unicode characters across different languages and scripts.
  • D. DUS
    DUS is the three-letter IATA code for Düsseldorf Airport, a major international airport in western Germany.
  • E. DU
    DU is a premier public central university in India, renowned for its diverse academic programs and large collegiate system based in New Delhi.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e05031f6a08190bfb333eced0a59a1 completed April 16, 2026, 2:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff9096d65c81908755cae83cc48e61 completed May 9, 2026, 7:52 p.m.
Created at: April 10, 2026, 4:47 a.m.