Triple
T28912915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krewella |
E733278
|
entity |
| Predicate | notableFestivalAppearance |
P116079
|
FINISHED |
| Object | Ultra Music Festival |
E199048
|
NE 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: Ultra Music Festival | Statement: [Krewella, notableFestivalAppearance, Ultra Music Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFestivalAppearance Context triple: [Krewella, notableFestivalAppearance, Ultra Music Festival]
-
A.
notableLivePerformanceEvent
Indicates that an entity is a significant or widely recognized live performance event associated with another entity (such as an artist, work, or venue).
-
B.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
-
C.
notableAppearance
Indicates that an entity is prominently featured or makes a significant appearance in another work, event, or context.
-
D.
festivalPresence
chosen
Indicates that an entity is present at, participates in, or is associated with a particular festival event.
-
E.
hasFestivalDepicted
Indicates that a work or representation includes a depiction or portrayal of a festival.
- F. None of above.
Provenance (4 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d417ab0081908293d81c9ddca899 |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: April 28, 2026, 8:12 a.m.