Triple
T31558910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brecon Jazz Festival |
E805203
|
entity |
| Predicate | musicSubgenreFeatured |
P191806
|
FINISHED |
| Object | traditional jazz |
—
|
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: traditional jazz | Statement: [Brecon Jazz Festival, musicSubgenreFeatured, traditional jazz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicSubgenreFeatured Context triple: [Brecon Jazz Festival, musicSubgenreFeatured, traditional jazz]
-
A.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
B.
musicForGenre
Indicates that something (such as a piece, track, or work) is intended to be used as or associated with music belonging to a particular genre.
-
C.
musicGenreObsessedWith
Indicates that one entity is intensely preoccupied with or fixated on a particular music genre.
-
D.
musicFeatured
Indicates that a particular piece of music is prominently included or used within another work, event, or context.
-
E.
musicGenreBroad
Indicates that one music genre is a broader, more general category that encompasses another, more specific music genre.
- F. None of above. chosen
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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 30, 2026, 10:14 p.m.