Triple
T30464746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Springsteen Seeger Sessions Tour |
E775103
|
entity |
| Predicate | featuresRepertoire |
P3738
|
FINISHED |
| Object | folk standards |
—
|
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 standards | Statement: [Bruce Springsteen Seeger Sessions Tour, featuresRepertoire, folk standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRepertoire Context triple: [Bruce Springsteen Seeger Sessions Tour, featuresRepertoire, folk standards]
-
A.
featuresRepertoireType
Indicates that something includes or is associated with a particular type or category of repertoire.
-
B.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
C.
featuresRichHarmonies
Indicates that the subject contains or employs complex, layered, and sonically dense harmonic structures.
-
D.
repertoireSource
Indicates that one entity serves as the origin or provider of the material, content, or items that make up another entity’s repertoire.
-
E.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: April 29, 2026, 8:11 p.m.