Triple

T1640708
Position Surface form Disambiguated ID Type / Status
Subject Haneda Airport E35463 entity
Predicate nativeName P15 FINISHED
Object 東京国際空港 E35463 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: [Haneda Airport, nativeName, 東京国際空港]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 東京国際空港
Context triple: [Haneda Airport, nativeName, 東京国際空港]
  • A. Narita International Airport
    Narita International Airport is a major international gateway to Japan and one of the primary airports serving the Greater Tokyo area.
  • B. Haneda Airport chosen
    Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
  • C. 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.
  • D. Kobe Airport
    Kobe Airport is a regional airport located on an artificial island off the coast of Kobe, Japan, primarily serving domestic flights.
  • E. 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.
  • 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_69a88604618c81908b41f6429c431eb6 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90a3c883c8190bec1d87ecedf2575 completed March 5, 2026, 4:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad609cf8488190ba334bdff2c5e78d completed March 8, 2026, 11:42 a.m.
Created at: March 4, 2026, 7:28 p.m.