Triple

T14948445
Position Surface form Disambiguated ID Type / Status
Subject Air Do E372727 entity
Predicate operatesRoute P3695 FINISHED
Object Sapporo–Tokyo Haneda
Sapporo–Tokyo Haneda is a major domestic air route in Japan connecting Hokkaido’s capital with Tokyo’s centrally located Haneda Airport.
 E1163736 NE FINISHED

How this triple was built (4 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: Sapporo–Tokyo Haneda | Statement: [Air Do, operatesRoute, Sapporo–Tokyo Haneda]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Sapporo–Tokyo Haneda
Context triple: [Air Do, operatesRoute, Sapporo–Tokyo Haneda]
  • A. 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.
  • B. 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.
  • C. Fukuoka–Tokyo Haneda
    Fukuoka–Tokyo Haneda is a major domestic air route in Japan connecting Fukuoka in Kyushu with Tokyo’s centrally located Haneda Airport.
  • D. Haneda Airport
    Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
  • E. Haneda
    Haneda is a Japanese surname commonly borne by individuals in Japan.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Sapporo–Tokyo Haneda
Triple: [Air Do, operatesRoute, Sapporo–Tokyo Haneda]
Generated description
Sapporo–Tokyo Haneda is a major domestic air route in Japan connecting Hokkaido’s capital with Tokyo’s centrally located Haneda Airport.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Sapporo–Tokyo Haneda
Target entity description: Sapporo–Tokyo Haneda is a major domestic air route in Japan connecting Hokkaido’s capital with Tokyo’s centrally located Haneda Airport.
  • A. 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.
  • B. 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.
  • C. Fukuoka–Tokyo Haneda
    Fukuoka–Tokyo Haneda is a major domestic air route in Japan connecting Fukuoka in Kyushu with Tokyo’s centrally located Haneda Airport.
  • D. Haneda Airport
    Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
  • E. Haneda
    Haneda is a Japanese surname commonly borne by individuals in Japan.
  • F. None of above. chosen

Provenance (5 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_69d85cca979481908747d2a81eba1cea completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded68e35c481908e47cd68441c5115 completed April 15, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff45406c8c8190beb87d4bb5c50355 completed May 9, 2026, 2:31 p.m.
NEDg Description generation batch_69ff471cb68c8190924e894b190f15f4 completed May 9, 2026, 2:39 p.m.
NED2 Entity disambiguation (via description) batch_69ff47aeddac8190a87024019ecb1396 completed May 9, 2026, 2:41 p.m.
Created at: April 10, 2026, 2:39 a.m.