Triple
T32759982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spark |
E837729
|
entity |
| Predicate | isPopularInEDMFestivals |
P175087
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Spark, isPopularInEDMFestivals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularInEDMFestivals Context triple: [The Spark, isPopularInEDMFestivals, true]
-
A.
hasFestivalImportance
Indicates that something holds notable significance, relevance, or prominence within the context of a festival or festive event.
-
B.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
C.
isFestivalFriendly
Indicates that something is suitable, welcoming, or appropriate for attending or participating in a festival.
-
D.
isPopularEDMTrack
chosen
Indicates that a track is widely liked, frequently played, or well-known within the electronic dance music (EDM) scene.
-
E.
locatedInFestival
Indicates that something exists or takes place within the spatial or organizational boundaries of a specific festival.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:13 a.m.