Triple
T38229612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blown Away Tour |
E1012246
|
entity |
| Predicate | hasSetDesignFeature |
P177101
|
FINISHED |
| Object | storm-themed visuals |
—
|
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: storm-themed visuals | Statement: [Blown Away Tour, hasSetDesignFeature, storm-themed visuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetDesignFeature Context triple: [Blown Away Tour, hasSetDesignFeature, storm-themed visuals]
-
A.
hasSetDesign
Indicates that something possesses or is associated with a particular set design, typically defining the visual or physical layout of a scene or environment.
-
B.
hasDesignProperty
chosen
Indicates that an entity possesses a specific design-related characteristic, feature, or attribute.
-
C.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 3, 2026, 4:30 p.m.