Triple
T27188130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castaway Cay |
E683392
|
entity |
| Predicate | exclusiveFor |
P43059
|
FINISHED |
| Object | Disney Cruise Line passengers |
—
|
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: Disney Cruise Line passengers | Statement: [Castaway Cay, exclusiveFor, Disney Cruise Line passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exclusiveFor Context triple: [Castaway Cay, exclusiveFor, Disney Cruise Line passengers]
-
A.
exclusiveTo
chosen
Indicates that something is restricted or limited to a specific entity, group, or context and not shared with others.
-
B.
exclusive
Indicates that the relationship or action applies only to a specific entity or set of entities, excluding all others from sharing that same status or participation.
-
C.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
D.
brandExclusive
Indicates that something is restricted to, offered only by, or uniquely associated with a single brand.
-
E.
exclusivityLevel
Indicates the degree to which something is restricted to a limited set of entities, uses, or contexts, excluding others.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 9:31 a.m.