Triple
T28632993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka–Tokyo Haneda |
E724694
|
entity |
| Predicate | centralAirportForTokyo |
P180421
|
FINISHED |
| Object | Haneda Airport |
—
|
NE NERFINISHED |
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: [Fukuoka–Tokyo Haneda, centralAirportForTokyo, Haneda Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralAirportForTokyo Context triple: [Fukuoka–Tokyo Haneda, centralAirportForTokyo, Haneda Airport]
-
A.
hubAirport
Indicates that an airport serves as a primary hub or central operating base for a particular airline or carrier.
-
B.
subprefectureCapital
Indicates that one entity serves as the administrative capital or seat of government for a given subprefecture.
-
C.
hubAirportCity
Indicates that a city serves as a primary hub location for an airport or airline.
-
D.
TokyoMetroStationNumber
Indicates that an entity is assigned a specific official station number within the Tokyo Metro railway network.
-
E.
locatedInDirectionFromTokyo
Indicates that one place is situated in a specified compass direction relative to Tokyo.
- F. None of above. chosen
Provenance (4 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 28, 2026, 4:38 a.m.