Triple

T8354666
Position Surface form Disambiguated ID Type / Status
Subject 中部地方 E196653 entity
Predicate hasAirport P105 FINISHED
Object 中部国際空港 E382205 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: 中部国際空港 | Statement: [中部地方, hasAirport, 中部国際空港]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 中部国際空港
Context triple: [中部地方, hasAirport, 中部国際空港]
  • A. 中部国際空港 chosen
    中部国際空港 is a major international airport built on an artificial island in Ise Bay serving the Nagoya metropolitan area and Japan’s Chūbu region.
  • B. Kansai International Airport
    Kansai International Airport is a major international airport in Japan built on an artificial island in Osaka Bay, serving as a key gateway to the Kansai region.
  • C. Kobe Airport
    Kobe Airport is a regional airport located on an artificial island off the coast of Kobe, Japan, primarily serving domestic flights.
  • D. Osaka International Airport
    Osaka International Airport is a major Japanese airport serving the Osaka metropolitan area, primarily handling domestic flights and known locally as Itami Airport.
  • E. Clow International Airport
    Clow International Airport is a public general aviation airport located in Bolingbrook, Illinois, primarily serving private and recreational pilots.
  • 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_69ca82f08b348190bfb7881944bbff6f completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb8048edb88190a1980ad74818b898 completed March 31, 2026, 8:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc75e94288190ba1905dd4ca172dd completed April 2, 2026, 1:33 a.m.
Created at: March 30, 2026, 5:59 p.m.