Triple
T26037066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaton Sound festival site |
E647581
|
entity |
| Predicate | festivalGenreFocus |
P105215
|
FINISHED |
| Object | electronic dance music |
—
|
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: electronic dance music | Statement: [Balaton Sound festival site, festivalGenreFocus, electronic dance music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: festivalGenreFocus Context triple: [Balaton Sound festival site, festivalGenreFocus, electronic dance music]
-
A.
festivalFocus
Indicates that a festival is centered around, dedicated to, or thematically focused on a particular subject, activity, or feature.
-
B.
hasFestivalGenre
chosen
Indicates that a festival is associated with or categorized under a particular genre.
-
C.
festivalFeature
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
-
D.
festivalAttracts
Indicates that a festival draws or brings in attendees, participants, or interest toward itself.
-
E.
festivalSeason
Indicates that a time period is designated or recognized as the season during which a particular festival or set of festivals takes 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6061e95848190b6a47fd49280ad1c |
completed | May 2, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:08 a.m.