Triple
T21009758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitakyushu Airport |
E517512
|
entity |
| Predicate | primaryDomesticDestination |
P142461
|
FINISHED |
| Object | Tokyo (Haneda Airport) |
—
|
NE NERFINISHED |
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: Tokyo (Haneda Airport) | Statement: [Kitakyushu Airport, primaryDomesticDestination, Tokyo (Haneda Airport)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tokyo (Haneda Airport) Context triple: [Kitakyushu Airport, primaryDomesticDestination, Tokyo (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.
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.
-
D.
Haneda
Haneda is a Japanese surname commonly borne by individuals in Japan.
-
E.
Wakkanai–Tokyo Haneda
Wakkanai–Tokyo Haneda is a domestic air route in Japan connecting Wakkanai in northern Hokkaido with Tokyo’s Haneda Airport.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Tokyo (Haneda Airport) Target entity description: Tokyo (Haneda Airport) is one of Japan’s main airports, serving as a major domestic and international hub for the Tokyo metropolitan area.
-
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.
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.
-
D.
Haneda
Haneda is a Japanese surname commonly borne by individuals in Japan.
-
E.
Wakkanai–Tokyo Haneda
Wakkanai–Tokyo Haneda is a domestic air route in Japan connecting Wakkanai in northern Hokkaido with Tokyo’s Haneda Airport.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDomesticDestination Context triple: [Kitakyushu Airport, primaryDomesticDestination, Tokyo (Haneda Airport)]
-
A.
primaryFreightDestination
Indicates the main location to which freight is intended to be shipped or delivered.
-
B.
primaryDestinationsType
Indicates the type or category of main destinations associated with an entity or activity.
-
C.
primaryRouteCountry
Indicates the country that serves as the main or principal route location associated with the subject.
-
D.
primaryUSDestination
Indicates that an entity’s main or most significant destination within the United States is the specified location.
-
E.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
- F. None of above. chosen
Provenance (4 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3edc548190987a6c2c9936286a |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:53 p.m.