Triple
T10560320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straw Bear Festival |
E249199
|
entity |
| Predicate | usesMusicGenre |
P33180
|
FINISHED |
| Object | folk 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: folk music | Statement: [Straw Bear Festival, usesMusicGenre, folk music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMusicGenre Context triple: [Straw Bear Festival, usesMusicGenre, folk music]
-
A.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
B.
styleOfMusic
chosen
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
C.
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.
-
D.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
-
E.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271f3c6c819080b49fbe3aa09e09 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.