Triple
T26944219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney Magic |
E678593
|
entity |
| Predicate | hasEntertainmentBrand |
P170366
|
FINISHED |
| Object | Disney Cruise Line entertainment |
—
|
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 entertainment | Statement: [Disney Magic, hasEntertainmentBrand, Disney Cruise Line entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntertainmentBrand Context triple: [Disney Magic, hasEntertainmentBrand, Disney Cruise Line entertainment]
-
A.
hasEventBrand
Indicates that an event is associated with or organized under a particular brand.
-
B.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
C.
hasTelevisionChannelBrand
Indicates that an entity is associated with or operates under a particular television channel brand.
-
D.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
-
E.
hasStreamingServiceBrandExtension
Indicates that a brand has extended into offering a streaming service under its name or umbrella.
- F. None of above. chosen
Provenance (4 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_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 6:20 a.m.