Triple
T29451733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tree of Wooden Clogs |
E746991
|
entity |
| Predicate | musicScoreType |
P181422
|
FINISHED |
| Object | primarily diegetic 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: primarily diegetic folk music | Statement: [The Tree of Wooden Clogs, musicScoreType, primarily diegetic folk music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicScoreType Context triple: [The Tree of Wooden Clogs, musicScoreType, primarily diegetic folk music]
-
A.
musicScoreBy
Indicates that a musical score was created or composed by a particular agent or entity.
-
B.
hasSheetMusicAvailability
Indicates that there exists accessible sheet music associated with the referenced musical work or performance.
-
C.
musicalSymbol
Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
-
D.
sheetMusicPublishedIn
Indicates that a piece of sheet music was published in a specific location, medium, or publication context.
-
E.
hasNoMusicalScore
Indicates that something lacks an associated musical score or written musical accompaniment.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 28, 2026, 3:33 p.m.