Triple

T3310511
Position Surface form Disambiguated ID Type / Status
Subject Western Japan E69559 entity
Predicate hasMajorAirport P281 FINISHED
Object Hiroshima Airport E178097 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: Hiroshima Airport | Statement: [Western Japan, hasMajorAirport, Hiroshima Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hiroshima Airport
Context triple: [Western Japan, hasMajorAirport, Hiroshima Airport]
  • A. Hiroshima Airport chosen
    Hiroshima Airport is the main regional airport serving Hiroshima Prefecture in Japan, handling domestic and limited international flights.
  • B. Nagasaki Airport
    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.
  • C. Okayama Airport
    Okayama Airport is a regional international airport in Okayama Prefecture, Japan, serving domestic routes and select international destinations in the Chūgoku area.
  • D. Itami Airport
    Itami Airport is a major domestic airport serving the Osaka metropolitan area in Japan.
  • E. Okadama Airport
    Okadama Airport is a regional airport in Sapporo, Japan, primarily serving domestic and general aviation flights.
  • 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_69ad859f218081909458d2cebbf57565 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0eb6dd08190bab1ce80f417966a completed March 8, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69b402c197c88190b0ca5a7f47141511 completed March 13, 2026, 12:27 p.m.
Created at: March 8, 2026, 3:11 p.m.