Triple
T14972445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tama River |
E373354
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Haneda Airport |
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 Airport | Statement: [Tama River, near, Haneda Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haneda Airport Context triple: [Tama River, near, Haneda Airport]
-
A.
Haneda Airport
chosen
Haneda Airport is one of Tokyo’s primary international airports and one of Japan’s busiest air travel hubs.
-
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.
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.
-
D.
Narita International Airport
Narita International Airport is a major international gateway to Japan and one of the primary airports serving the Greater Tokyo area.
-
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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e767608190940eb6f16ea97451 |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa92b99c48190b76e1306cf32a568 |
completed | May 9, 2026, 9:37 p.m. |
Created at: April 10, 2026, 2:50 a.m.