Triple
T26496941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billund Airport |
E669306
|
entity |
| Predicate | hasDutyFreeShopping |
P40354
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Billund Airport, hasDutyFreeShopping, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDutyFreeShopping Context triple: [Billund Airport, hasDutyFreeShopping, yes]
-
A.
hasDutyFreeArea
chosen
Indicates that one entity provides or contains a designated duty-free area for another entity or for certain activities.
-
B.
isTaxFreeShoppingDestination
Indicates that a location is designated as a place where shoppers can purchase goods without paying certain taxes (e.g., sales or value-added tax).
-
C.
hasTaxFreeCounter
Indicates that an entity possesses or is associated with a counter or tally that is exempt from taxes.
-
D.
hasCustomsCheckpoint
Indicates that a location or route includes an official customs inspection point where goods, vehicles, or people are checked for compliance with border regulations.
-
E.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613573c548190a4a25a430a89fbf4 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:09 a.m.