Triple
T8887917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | runway system of Kansai International Airport |
E211580
|
entity |
| Predicate | openedWithAirport |
P17227
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [runway system of Kansai International Airport, openedWithAirport, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedWithAirport Context triple: [runway system of Kansai International Airport, openedWithAirport, 1994]
-
A.
openedAsCivilAirport
Indicates that a facility or location began operation specifically as a civil (non-military) airport.
-
B.
openedAsMainAirport
Indicates that an airport was inaugurated or began operation specifically in the role of the primary or principal airport for a given city or region.
-
C.
openedAsInternationalAirport
Indicates that an airport was inaugurated or began operations specifically as an international airport, serving international flights from its opening.
-
D.
openedAsMunicipalAirport
Indicates that an airport was initially established and began operation as a municipal (city- or town-operated) airport.
-
E.
airportOpened
chosen
Indicates that an airport began operations or was officially opened at a specific time.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618e58d08190be3ebcbe3701b1db |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.