Triple

T30028003
Position Surface form Disambiguated ID Type / Status
Subject Mainstage (Tomorrowland) E762932 entity
Predicate pyrotechnicElement P45831 FINISHED
Object fire effects 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: fire effects | Statement: [Mainstage (Tomorrowland), pyrotechnicElement, fire effects]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pyrotechnicElement
Context triple: [Mainstage (Tomorrowland), pyrotechnicElement, fire effects]
  • A. hasPyrotechnics chosen
    Indicates that an entity includes, uses, or features pyrotechnic effects or fireworks as part of its characteristics or activities.
  • B. fireworksCompany
    Indicates a relationship where an entity is a company that produces, sells, or organizes fireworks displays for another entity or context.
  • C. explosiveComponents
    Indicates that one entity consists of, contains, or is associated with components that are explosive or used to create an explosive device.
  • D. explosiveMaterialUsed
    Indicates that an explosive material was employed or involved in carrying out a particular action or event.
  • E. explosionDesignation
    Indicates that an entity is assigned a specific designation or label associated with an explosion event or explosive classification.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f679ad19f88190a01d97605aecb0d8 completed May 2, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69f66ec9919881908a187bfc7c4df192 completed May 2, 2026, 9:38 p.m.
Created at: April 29, 2026, 6:49 p.m.