Triple
T11855445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōta, Tokyo |
E282024
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Haneda |
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: Haneda | Statement: [Ōta, Tokyo, contains, Haneda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haneda Context triple: [Ōta, Tokyo, contains, 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.
Haneda Airport
chosen
Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
-
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.
Tezu Airport
Tezu Airport is a regional airport in Arunachal Pradesh, India, serving the town of Tezu and improving air connectivity in the remote northeastern 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a697f4108190af984932d2118472 |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f41798b5888190b615d4e23fe3d55e |
completed | May 1, 2026, 3:01 a.m. |
Created at: April 8, 2026, 9:43 p.m.