Triple
T29227170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Under the Electric Sky |
E740962
|
entity |
| Predicate | musicFestivalFeatured |
P96461
|
FINISHED |
| Object | Electric Daisy Carnival |
—
|
NE NERFINISHED |
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: Electric Daisy Carnival | Statement: [Under the Electric Sky, musicFestivalFeatured, Electric Daisy Carnival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicFestivalFeatured Context triple: [Under the Electric Sky, musicFestivalFeatured, Electric Daisy Carnival]
-
A.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
B.
festivalCalendar
Indicates that there is a scheduled festival or celebration associated with a particular time or date in a calendar.
-
C.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
D.
festivalFunction
Indicates that an event serves as a festival or is functioning in the role of a festival within a given context.
-
E.
festivalActivity
Indicates that an entity is an event, performance, or engagement that takes place as part of a festival’s organized program.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 12:17 p.m.