Triple
T19663175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean (fictional country) |
E472134
|
entity |
| Predicate | hasTouristicImage |
P63888
|
FINISHED |
| Object | vacation destination |
—
|
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: vacation destination | Statement: [Caribbean (fictional country), hasTouristicImage, vacation destination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristicImage Context triple: [Caribbean (fictional country), hasTouristicImage, vacation destination]
-
A.
tourismImage
chosen
Indicates a relationship where something serves as a visual representation or promotional image associated with tourism for a place, attraction, or destination.
-
B.
hasPhotoSpot
Indicates that a location or entity includes or is associated with a designated place suitable for taking photographs.
-
C.
photographedByTourists
Indicates that the subject has been photographed by people visiting as tourists.
-
D.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
E.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416671fc81908e25b0477234fa0f |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.