Triple

T10977625
Position Surface form Disambiguated ID Type / Status
Subject Yap International Airport E259412 entity
Predicate IATAcode P418 FINISHED
Object YAP E824959 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: YAP | Statement: [Yap International Airport, IATAcode, YAP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YAP
Context triple: [Yap International Airport, IATAcode, YAP]
  • A. Yapak
    Yapak is a barangay on Boracay Island in the Philippines, known for its quieter atmosphere, scenic beaches, and natural attractions compared to the island’s busier areas.
  • B. Yap Time chosen
    Yap Time is the time zone observed in Yap, one of the states of the Federated States of Micronesia in the western Pacific Ocean.
  • C. YIP
    YIP is the IATA airport code for Willow Run Airport, a cargo-focused and general aviation airport near Ypsilanti, Michigan, in the United States.
  • D. YDP
    YDP is the IATA airport code for Nain Airport, a regional airport serving the community of Nain in Newfoundland and Labrador, Canada.
  • E. YAM
    YAM is the IATA airport code for Sault Ste. Marie Airport in Ontario, Canada.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d771f6a9448190b3932ee801ae0da9 completed April 9, 2026, 9:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2d7bcea448190b09906c79de67496 completed April 18, 2026, 1 a.m.
Created at: April 8, 2026, 9:24 p.m.