Triple
T16756163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaboom Town! |
E407209
|
entity |
| Predicate | typeOfFireworksShow |
P7504
|
FINISHED |
| Object | professionally produced pyrotechnic display |
—
|
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: professionally produced pyrotechnic display | Statement: [Kaboom Town!, typeOfFireworksShow, professionally produced pyrotechnic display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFireworksShow Context triple: [Kaboom Town!, typeOfFireworksShow, professionally produced pyrotechnic display]
-
A.
hasPyrotechnics
Indicates that an entity includes, uses, or features pyrotechnic effects or fireworks as part of its characteristics or activities.
-
B.
typeOfEvent
chosen
Indicates that one entity is classified as a specific kind or category of event.
-
C.
typeOfPerformances
Indicates the kinds or categories of performances associated with or offered by an entity.
-
D.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
E.
fireworksDisplayDate
Indicates the date on which a fireworks display is scheduled to occur or took place.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe831ec8190bac05b07db6153c1 |
completed | April 18, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.