Triple
T1732743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiestas de la Calle San Sebastián |
E37849
|
entity |
| Predicate | typicalMusicGenre |
P13889
|
FINISHED |
| Object | salsa |
—
|
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: salsa | Statement: [Fiestas de la Calle San Sebastián, typicalMusicGenre, salsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMusicGenre Context triple: [Fiestas de la Calle San Sebastián, typicalMusicGenre, salsa]
-
A.
isPopularMusic
Indicates that the subject is a type of music that enjoys widespread appeal or mainstream popularity among listeners.
-
B.
genreRecognized
chosen
Indicates that a particular genre has been identified or acknowledged as applicable to an entity.
-
C.
knownForMusicGenre
Indicates that an entity is recognized or notable for producing, performing, or being associated with a particular music genre.
-
D.
songType
Indicates the specific category or genre that a given song belongs to.
-
E.
genreContext
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.