Triple
T9236642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What’s New |
E221952
|
entity |
| Predicate | featuresSongType |
P9125
|
FINISHED |
| Object | Great American Songbook 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: Great American Songbook standards | Statement: [What’s New, featuresSongType, Great American Songbook standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSongType Context triple: [What’s New, featuresSongType, Great American Songbook standards]
-
A.
songType
Indicates the specific category or genre that a given song belongs to.
-
B.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
C.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
-
D.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
E.
notableSongCharacteristic
chosen
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09e553081909cf864635cfc5dcc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.