Triple
T24786916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fornebu |
E620142
|
entity |
| Predicate | airportReplacedBy |
P29669
|
FINISHED |
| Object | Oslo Airport, Gardermoen |
—
|
NE NERFINISHED |
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: Oslo Airport, Gardermoen | Statement: [Fornebu, airportReplacedBy, Oslo Airport, Gardermoen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportReplacedBy Context triple: [Fornebu, airportReplacedBy, Oslo Airport, Gardermoen]
-
A.
airportLinkReplaced
Indicates that one airport rail or transit link has been superseded or taken over in function by another link.
-
B.
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.
-
C.
associatedAirportReplaced
Indicates that one airport in an association has been superseded or replaced by another airport.
-
D.
airportNameChangedTo
Indicates that an airport’s official name has been changed from a previous name to a new specified name.
-
E.
hasFormerNearbyAirportName
Indicates that an entity previously had a nearby airport known by a different name than its current nearby airport name.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:46 a.m.