Triple
T35695802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Båtsfjord Airport |
E1031435
|
entity |
| Predicate | hasSTOLOperations |
P27737
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Båtsfjord Airport, hasSTOLOperations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSTOLOperations Context triple: [Båtsfjord Airport, hasSTOLOperations, true]
-
A.
hasPassengerOperations
Indicates that an entity conducts or supports transportation services specifically for carrying passengers.
-
B.
hasStalls
Indicates that an entity contains, provides, or is equipped with stalls (e.g., booths, compartments, or vendor stands).
-
C.
hasRollOnRollOffCapability
Indicates that an entity is capable of loading, transporting, or unloading cargo or vehicles using a roll-on/roll-off (Ro-Ro) method.
-
D.
hasRunwayOperations
chosen
Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
-
E.
hasCargoHandlingMode
Indicates the method or procedure by which cargo is handled, loaded, or unloaded in a given context.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:05 p.m.