Triple
T6066264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyongyang Sunan International Airport |
E135167
|
entity |
| Predicate | isCivilMilitaryAirport |
P34628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pyongyang Sunan International Airport, isCivilMilitaryAirport, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilMilitaryAirport Context triple: [Pyongyang Sunan International Airport, isCivilMilitaryAirport, true]
-
A.
isCivilAirport
Indicates that an airport is designated and used primarily for civilian (non-military) aviation operations.
-
B.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
C.
airportServesMilitaryTraffic
chosen
Indicates that the airport accommodates or handles military air traffic in addition to any other types of traffic.
-
D.
isMajorCargoAirport
Indicates that an airport primarily handles large volumes of cargo traffic and serves as a significant freight hub.
-
E.
isOnlyCommercialAirportIn
Indicates that an airport is the sole commercial airport serving a specified geographic area or region.
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0573df7508190bbb5b496188b2f3e |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.