Triple
T22133430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oulu Airport |
E546963
|
entity |
| Predicate | isMajorRegionalAirportIn |
P75084
|
FINISHED |
| Object | northern Finland |
—
|
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: northern Finland | Statement: [Oulu Airport, isMajorRegionalAirportIn, northern Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorRegionalAirportIn Context triple: [Oulu Airport, isMajorRegionalAirportIn, northern Finland]
-
A.
isMajorRegionalAirportFor
chosen
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
B.
isRegionalAirport
Indicates that an airport serves a specific region or local area rather than functioning as a major national or international hub.
-
C.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
D.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
-
E.
isMajorCargoAirport
Indicates that an airport primarily handles large volumes of cargo traffic and serves as a significant freight hub.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b81d5c819085fd18bf3ae28333 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.