Triple
T34265371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Doubt – Sunday Morning |
E879151
|
entity |
| Predicate | hasOriginBandType |
P197246
|
FINISHED |
| Object | American rock band |
—
|
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 rock band | Statement: [No Doubt – Sunday Morning, hasOriginBandType, American rock band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginBandType Context triple: [No Doubt – Sunday Morning, hasOriginBandType, American rock band]
-
A.
hasOriginBand
Indicates that an entity (such as a musician or musical act) is or was originally a member of a specified band.
-
B.
originatedFromBand
Indicates that an entity (such as a musician or group) originally came from or was formed as part of a particular band.
-
C.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
D.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
E.
hasOriginalBandNameOf
Indicates that one entity is the original band name used by another musical group or artist.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
| PDg | Predicate description generation | batch_69fe7eb31b04819081be531fd9f8a78c |
completed | May 9, 2026, 12:24 a.m. |
Created at: May 1, 2026, 1:56 a.m.