Triple
T21000109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Airport, Fornebu |
E517261
|
entity |
| Predicate | wasReplacedAsMainAirportInYear |
P29669
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Oslo Airport, Fornebu, wasReplacedAsMainAirportInYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReplacedAsMainAirportInYear Context triple: [Oslo Airport, Fornebu, wasReplacedAsMainAirportInYear, 1998]
-
A.
replacedAsMainAirportFor
chosen
Indicates that one airport has taken over the role of being the primary or main airport serving a particular area from another airport.
-
B.
associatedAirportReplaced
Indicates that one airport in an association has been superseded or replaced by another airport.
-
C.
openedAsNewAirportFor
Indicates that one airport was inaugurated to serve as a new replacement or successor facility for another airport.
-
D.
hasFormerAirport
Indicates that an entity previously had an airport that is no longer in operation or no longer exists.
-
E.
replacedAtAirportBy
Indicates that one entity is substituted or exchanged for another specifically at an airport.
- 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc24a6dc8190a6bf81cf1d9590c0 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.