Triple
T10871792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Out Islands of the Bahamas |
E256670
|
entity |
| Predicate | targetTouristSegment |
P1769
|
FINISHED |
| Object | visitors seeking seclusion |
—
|
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: visitors seeking seclusion | Statement: [Out Islands of the Bahamas, targetTouristSegment, visitors seeking seclusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTouristSegment Context triple: [Out Islands of the Bahamas, targetTouristSegment, visitors seeking seclusion]
-
A.
passengerSegments
Indicates a relationship where a journey or trip is divided into distinct legs or segments that a passenger travels through.
-
B.
tourismTrend
Indicates how patterns or levels of tourism activity change over time or across locations.
-
C.
subjectOfTour
Indicates that an entity serves as the main focus, destination, or theme of a tour.
-
D.
hasTouristProfile
Indicates that an entity possesses characteristics, data, or attributes defining it as a tourist or related to tourism behavior.
-
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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75186e75c8190bf046ea666faff54 |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.