Triple

T8174342
Position Surface form Disambiguated ID Type / Status
Subject NRT E190904 entity
Predicate airportName P4100 FINISHED
Object Narita International Airport E36529 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: Narita International Airport | Statement: [NRT, airportName, Narita International Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narita International Airport
Context triple: [NRT, airportName, Narita International Airport]
  • A. Narita International Airport chosen
    Narita International Airport is a major international gateway to Japan and one of the primary airports serving the Greater Tokyo area.
  • B. Haneda Airport
    Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
  • C. Naha–Tokyo Haneda
    Naha–Tokyo Haneda is a major domestic air route in Japan connecting Okinawa’s capital Naha with Tokyo’s centrally located Haneda Airport.
  • D. Miyazaki–Tokyo Haneda
    Miyazaki–Tokyo Haneda is a domestic air route in Japan connecting Miyazaki Airport on Kyushu with Tokyo’s centrally located Haneda Airport.
  • E. 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.
  • 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_69ca82c1c0a08190bf8692b4d91a03ca completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb480a7ac4819088fabd5bec6ba2e5 completed March 31, 2026, 4:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfeace262881909dedeb1a07e95279 completed April 3, 2026, 4:29 p.m.
Created at: March 30, 2026, 5:40 p.m.