Triple
T9329750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Something's Gotta Give |
E224485
|
entity |
| Predicate | hasMusicStandardStatus |
P44121
|
FINISHED |
| Object | American songbook standard |
—
|
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: American songbook standard | Statement: [Something's Gotta Give, hasMusicStandardStatus, American songbook standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicStandardStatus Context triple: [Something's Gotta Give, hasMusicStandardStatus, American songbook standard]
-
A.
hasISRCStatus
Indicates that an entity has a specific International Standard Recording Code (ISRC) status assigned or associated with it.
-
B.
hasMusicCharacteristic
chosen
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
E.
hasISRC
Indicates that a musical recording is associated with a specific International Standard Recording Code (ISRC) that uniquely identifies it.
- 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_69ca8427a0c08190b749831d5ea98f02 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37acbc04819092a67d7f392c74cd |
completed | April 1, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:39 p.m.