Triple
T27531712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyric Suite |
E694988
|
entity |
| Predicate | incorporatesNorwegianFolkElements |
P85135
|
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: [Lyric Suite, incorporatesNorwegianFolkElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incorporatesNorwegianFolkElements Context triple: [Lyric Suite, incorporatesNorwegianFolkElements, true]
-
A.
usesFolkMaterial
chosen
Indicates that one entity incorporates or draws upon traditional folk materials, such as melodies, stories, or motifs, in relation to another entity.
-
B.
usesWorldMusicElements
Indicates that something incorporates stylistic, rhythmic, melodic, or instrumental features associated with musical traditions from various cultures around the world.
-
C.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music genre.
-
D.
includesFolklore
Indicates that one entity contains, incorporates, or features folklore as part of its content or composition.
-
E.
isFolkSongFrom
Indicates that a folk song originates from or is traditionally associated with a particular place, region, or culture.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:26 p.m.