Triple
T16092682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barlavento Islands |
E390395
|
entity |
| Predicate | tourismHighlight |
P33214
|
FINISHED |
| Object | Sal beaches |
—
|
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: Sal beaches | Statement: [Barlavento Islands, tourismHighlight, Sal beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismHighlight Context triple: [Barlavento Islands, tourismHighlight, Sal beaches]
-
A.
tourismFeature
chosen
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
C.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
D.
tourismTrend
Indicates how patterns or levels of tourism activity change over time or across locations.
-
E.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.