Triple

T16404933
Position Surface form Disambiguated ID Type / Status
Subject Ōmura E398401 entity
Predicate hostsFacility P12416 FINISHED
Object Nagasaki Airport E87327 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: Nagasaki Airport | Statement: [Ōmura, hostsFacility, Nagasaki Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nagasaki Airport
Context triple: [Ōmura, hostsFacility, Nagasaki Airport]
  • A. Nagasaki Airport chosen
    Nagasaki Airport is a regional and international airport in Nagasaki Prefecture, Japan, notable for being one of the world’s first offshore airports built on an artificial island.
  • B. Hiroshima Nishi Airport
    Hiroshima Nishi Airport is a regional airport in Hiroshima, Japan, that primarily serves domestic flights and general aviation.
  • C. Hiroshima Airport
    Hiroshima Airport is the main regional airport serving Hiroshima Prefecture in Japan, handling domestic and limited international flights.
  • D. Niigata Airport
    Niigata Airport is a regional and international airport serving the city of Niigata in Japan’s Hokuriku region, offering domestic flights and select international routes.
  • E. Miyazaki Airport
    Miyazaki Airport is a regional airport in Miyazaki Prefecture, Japan, serving domestic flights and limited international routes for the city and surrounding area.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327d1f16481909adb19dab86dcc72 completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00c794355881908fdec356d12a5635 completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:09 a.m.