Triple

T8369209
Position Surface form Disambiguated ID Type / Status
Subject VVNB E197410 entity
Predicate hasIataCode P2569 FINISHED
Object HAN E197409 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: HAN | Statement: [VVNB, hasIataCode, HAN]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: HAN
Context triple: [VVNB, hasIataCode, HAN]
  • A. HAN
    HAN is the standard abbreviation used for the Hanshin Tigers, a professional baseball team in Japan's Nippon Professional Baseball league.
  • B. HAN chosen
    HAN is the IATA airport code for Noi Bai International Airport, the main international gateway serving Hanoi, Vietnam.
  • C. Han
    Han refers to the majority ethnic group in China, historically associated with Chinese civilization, language, and culture.
  • D. Han
    Han is a common transliteration of the historical Central Asian title "Khan," often associated with rulers and nobility in various Turkic and Mongolic cultures.
  • E. HANS
    HANS is the radio callsign used by Lufthansa CityLine, a regional airline within the Lufthansa Group.
  • 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_69ca82f56730819080cec5d991c76f4c completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb808f7c0481909fef5834cb6e7a3e completed March 31, 2026, 8:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde7d0a6d081909ffe138f80605992 completed April 2, 2026, 3:51 a.m.
Created at: March 30, 2026, 6:01 p.m.