Triple
T625639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maui |
E15811
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Hana Airport |
E62141
|
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: Hana Airport | Statement: [Maui, hasAirport, Hana Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hana Airport Context triple: [Maui, hasAirport, Hana Airport]
-
A.
Hana Airport
chosen
Hana Airport is a small regional airport serving the remote town of Hāna on the eastern coast of Maui, Hawaii.
-
B.
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.
-
C.
Kobe Airport
Kobe Airport is a regional airport located on an artificial island off the coast of Kobe, Japan, primarily serving domestic flights.
-
D.
Osaka International Airport
Osaka International Airport is a major Japanese airport serving the Osaka metropolitan area, primarily handling domestic flights and known locally as Itami 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5670380948190954bbdf802ed403c |
completed | March 2, 2026, 10:31 a.m. |
Created at: March 1, 2026, 7:35 p.m.