Triple
T35695816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Båtsfjord Airport |
E1031435
|
entity |
| Predicate | supportsMailServices |
P164762
|
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, supportsMailServices, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMailServices Context triple: [Båtsfjord Airport, supportsMailServices, true]
-
A.
hasMailServices
chosen
Indicates that an entity provides or supports mail-related services, such as sending, receiving, or handling postal or electronic mail.
-
B.
supportsPushEmail
Indicates that one entity provides or enables automatic, real-time delivery of email (push email) to another entity.
-
C.
supportsUserServices
Indicates that one entity provides the necessary functionality or resources for user-facing services to operate or be delivered.
-
D.
supportsMailFlights
Indicates that one entity provides the necessary facilities or services for mail-carrying flights to operate to or from another entity.
-
E.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.