Triple
T14219714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chōfu |
E352456
|
entity |
| Predicate | hasAirport |
P105
|
FINISHED |
| Object | Chōfu Airport |
E418503
|
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: Chōfu Airport | Statement: [Chōfu, hasAirport, Chōfu Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chōfu Airport Context triple: [Chōfu, hasAirport, Chōfu Airport]
-
A.
Chōfu Airport
chosen
Chōfu Airport is a regional airport in Tokyo, Japan, primarily serving domestic commuter and charter flights, including services to the Izu Islands.
-
B.
Ibaraki Airport
Ibaraki Airport is a regional civil airport in Ibaraki Prefecture, Japan, that operates alongside the adjacent Japan Air Self-Defense Force’s Hyakuri Air Base.
-
C.
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.
-
D.
Okadama Airport
Okadama Airport is a regional airport in Sapporo, Japan, primarily serving domestic and general aviation flights.
-
E.
Izumo Airport
Izumo Airport is a regional airport in Shimane Prefecture, Japan, providing domestic air services that connect the Izumo area with major Japanese cities.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4676a2bc8190af239516ddbbf5e3 |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:06 a.m.