Triple
T8174510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZIPAIR Tokyo |
E190907
|
entity |
| Predicate | operatesFromCity |
P60825
|
FINISHED |
| Object | Tokyo (Narita) |
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: Tokyo (Narita) | Statement: [ZIPAIR Tokyo, operatesFromCity, Tokyo (Narita)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tokyo (Narita) Context triple: [ZIPAIR Tokyo, operatesFromCity, Tokyo (Narita)]
-
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.
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.
-
D.
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.
-
E.
Haneda Airport
Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
- 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_69cef2b985888190a692f52cf5b93a80 |
completed | April 2, 2026, 10:50 p.m. |
Created at: March 30, 2026, 5:40 p.m.