Triple
T19625995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gimpo–Beijing Capital route |
E471135
|
entity |
| Predicate | departureAirportICAO |
P419
|
FINISHED |
| Object | RKSS |
—
|
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: RKSS | Statement: [Gimpo–Beijing Capital route, departureAirportICAO, RKSS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureAirportICAO Context triple: [Gimpo–Beijing Capital route, departureAirportICAO, RKSS]
-
A.
parentAirport
Indicates that one airport serves as the primary or overarching facility from which another, subsidiary or associated airport is derived or managed.
-
B.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
-
C.
airportNameOrigin
Indicates the name of the airport that serves as the origin point in a trip or flight-related relationship.
-
D.
typicalOriginAirportIATA
Indicates the usual or primary origin airport for an entity, identified by its IATA airport code.
-
E.
ICAOcode
chosen
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e9ff208190afb33c910ed2147b |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.