Triple
T630899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney's All-Star Music Resort |
E15923
|
entity |
| Predicate | hasDecorStyle |
P2788
|
FINISHED |
| Object | larger-than-life music icons |
—
|
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: larger-than-life music icons | Statement: [Disney's All-Star Music Resort, hasDecorStyle, larger-than-life music icons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecorStyle Context triple: [Disney's All-Star Music Resort, hasDecorStyle, larger-than-life music icons]
-
A.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
B.
hasSubstyle
Indicates that one style is a more specific or subordinate variant of another style within a hierarchical style structure.
-
C.
hasHigherStyleThan
Indicates that one entity’s style is considered superior or more fashionable than another’s.
-
D.
typeOfDecoration
chosen
Indicates the specific kind or style of decoration associated with an entity or applied in a given context.
-
E.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec171008190ab91dee86e9279af |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.