Triple

T25548324
Position Surface form Disambiguated ID Type / Status
Subject Stockholm Skavsta Airport E640368 entity
Predicate openedToCivilTraffic P84489 FINISHED
Object 1980s 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: 1980s | Statement: [Stockholm Skavsta Airport, openedToCivilTraffic, 1980s]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openedToCivilTraffic
Context triple: [Stockholm Skavsta Airport, openedToCivilTraffic, 1980s]
  • A. openedToCivilianTraffic chosen
    Indicates that a previously restricted or closed route, facility, or infrastructure has been made accessible for use by civilian (non-military) traffic.
  • B. openedToRoadTraffic
    Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
  • C. reopenedToTraffic
    Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
  • D. openedForThroughTraffic
    Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
  • E. openedToPassengerTraffic
    Indicates that a transportation facility or route began operating and accepting passengers for regular use.
  • 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_69e75dc101a881909fd33b02174e9768 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f62d89b89c8190afb372a8172111e7 completed May 2, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69f62c1379f08190836c3e02b0c892df completed May 2, 2026, 4:53 p.m.
Created at: April 21, 2026, 3:35 p.m.