Triple
T10921322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Bay Beach |
E257952
|
entity |
| Predicate | hasPrimaryTourismType |
P1769
|
FINISHED |
| Object | luxury beach tourism |
—
|
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: luxury beach tourism | Statement: [Grace Bay Beach, hasPrimaryTourismType, luxury beach tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTourismType Context triple: [Grace Bay Beach, hasPrimaryTourismType, luxury beach tourism]
-
A.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
B.
hasPrimaryAttractionType
Indicates that an entity is characterized by a main or dominant type of attraction or appeal it offers.
-
C.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
D.
hasTourismStyle
Indicates the type or style of tourism associated with or characteristic of a particular entity.
-
E.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77082a1488190850a4409339c3e1e |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d72e799f808190b6ab64fc7586a303 |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:22 p.m.