Triple
T11798687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Carnival |
E280567
|
entity |
| Predicate | hasComponentEvent |
P6285
|
FINISHED |
| Object | Panorama steelband competition |
—
|
NE GENERATED |
How this triple was built (1 step)
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Panorama steelband competition Context triple: [Miami Carnival, hasComponentEvent, Panorama steelband competition]
-
A.
Panorama steelband competition
chosen
The Panorama steelband competition is Trinidad and Tobago’s premier national steelpan music contest, held annually in Port of Spain and showcasing the country’s top steel orchestras.
-
B.
Carnival Parade of the Bands
Carnival Parade of the Bands is a major Trinidad and Tobago Carnival event where elaborately costumed masquerade bands cross the main stage in a vibrant competition of music, dance, and design.
-
C.
King and Queen of the Bands competition
The King and Queen of the Bands competition is a marquee Crop Over event in Barbados where elaborately costumed masqueraders vie for titles based on creativity, craftsmanship, and spectacle.
-
D.
Battle of the Bands
Battle of the Bands is a competitive live music event where multiple bands perform to win judges’ or audience approval, often featured as a climactic contest in rock and youth culture stories.
-
E.
Whit Friday brass band contests
The Whit Friday brass band contests are a series of traditional, competitive brass band performances held annually across towns in northern England, attracting bands and spectators from around the world.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (1 batch)
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.