Triple

T13614368
Position Surface form Disambiguated ID Type / Status
Subject Setesdal E325272 entity
Predicate hasTraditionalMusicForm P526 FINISHED
Object slått 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: slått music | Statement: [Setesdal, hasTraditionalMusicForm, slått music]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalMusicForm
Context triple: [Setesdal, hasTraditionalMusicForm, slått music]
  • A. hasMusicalForm
    Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
  • B. hasTraditionalFormIn
    Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
  • C. musicTradition chosen
    Indicates a relationship where one entity follows, embodies, or belongs to a particular musical tradition or style associated with another entity.
  • D. hasTraditionalDance
    Indicates that an entity is associated with, practices, or possesses a specific traditional dance.
  • E. basedInGenreTradition
    Indicates that something (such as a work or practice) is grounded in, follows, or is shaped by the conventions and traditions of a particular genre.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae1b3ee481909bd43ded6227a3e5 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:50 p.m.