Triple
T28184188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Haneda – Sapporo |
E716123
|
entity |
| Predicate | originAirportType |
P197292
|
FINISHED |
| Object | hub airport |
—
|
LITERAL 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: hub airport | Statement: [Tokyo Haneda – Sapporo, originAirportType, hub airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originAirportType Context triple: [Tokyo Haneda – Sapporo, originAirportType, hub airport]
-
A.
originAirportHub
Indicates that the referenced airport serves as a primary hub or main operating base for the associated airline or carrier.
-
B.
originAirportICAO
Indicates the airport, identified by its ICAO code, from which a flight or journey departs.
-
C.
typicalOriginAirportIATA
Indicates the usual or primary origin airport for an entity, identified by its IATA airport code.
-
D.
formerAirportType
Indicates that an entity previously had a specific airport classification or type, but no longer holds that status.
-
E.
parentAirport
Indicates that one airport serves as the primary or overarching facility from which another, subsidiary or associated airport is derived or managed.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: April 27, 2026, 10:21 p.m.