Triple
T26944243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Fantasy |
E678594
|
entity |
| Predicate | primaryItineraries |
P79601
|
FINISHED |
| Object | Caribbean cruises |
—
|
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: Caribbean cruises | Statement: [Disney Fantasy, primaryItineraries, Caribbean cruises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryItineraries Context triple: [Disney Fantasy, primaryItineraries, Caribbean cruises]
-
A.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
B.
travelRouteOf
chosen
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
C.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
D.
travelHub
Indicates a location that serves as a central node or major interchange point for travel or transportation connections between different places or routes.
-
E.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 27, 2026, 6:20 a.m.