Triple
T1927944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itami |
E40874
|
entity |
| Predicate | primaryAirportFunction |
P16381
|
FINISHED |
| Object | domestic flights hub for Kansai region |
—
|
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: domestic flights hub for Kansai region | Statement: [Itami, primaryAirportFunction, domestic flights hub for Kansai region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAirportFunction Context triple: [Itami, primaryAirportFunction, domestic flights hub for Kansai region]
-
A.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
B.
airportServesAs
chosen
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
C.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
D.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
E.
operatingBaseAirport
Indicates the airport that serves as the primary base of operations for an airline or aircraft.
- F. None of above.
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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb263cdb8819084d0bda98a2a71e0 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.