Triple
T25548342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm Skavsta Airport |
E640368
|
entity |
| Predicate | runway26Heading |
P70220
|
FINISHED |
| Object | approximately 260 degrees |
—
|
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: approximately 260 degrees | Statement: [Stockholm Skavsta Airport, runway26Heading, approximately 260 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway26Heading Context triple: [Stockholm Skavsta Airport, runway26Heading, approximately 260 degrees]
-
A.
runway06_24Use
Indicates the use or operation of runway 06/24 for aircraft movements or related runway activities.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runwayEndHeading
chosen
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
D.
runwayPlan
Indicates a planned or designated use of a runway for aircraft operations (such as takeoff, landing, or sequencing) within an airfield’s operational schedule.
-
E.
runwayCrosses
Indicates that one runway intersects or passes across another runway or designated path.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 3:35 p.m.