Triple
T22821410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mama Do (Uh Oh, Uh Oh) |
E565237
|
entity |
| Predicate | ISRCCode |
P15290
|
FINISHED |
| Object | GBUM70902440 |
—
|
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: GBUM70902440 | Statement: [Mama Do (Uh Oh, Uh Oh), ISRCCode, GBUM70902440]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISRCCode Context triple: [Mama Do (Uh Oh, Uh Oh), ISRCCode, GBUM70902440]
-
A.
hasISRC
chosen
Indicates that a musical recording is associated with a specific International Standard Recording Code (ISRC) that uniquely identifies it.
-
B.
hasISRCStatus
Indicates that an entity has a specific International Standard Recording Code (ISRC) status assigned or associated with it.
-
C.
ISRCWhitneyHoustonVersion
Indicates that the referenced item is the International Standard Recording Code specifically for the Whitney Houston version of a recording.
-
D.
hasISWC
Indicates that a musical work is associated with a specific International Standard Musical Work Code (ISWC) that uniquely identifies it.
-
E.
hasISWCStatus
Indicates that an entity has a specific ISWC (International Standard Musical Work Code) status assigned or associated with 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcffdd88190a5f9c780c71b5053 |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:33 p.m.