Triple
T37054160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Like Digging? (as Kara's Flowers) |
E917128
|
entity |
| Predicate | hasSuccessorBandName |
P148562
|
FINISHED |
| Object | Maroon 5 |
—
|
NE NERFINISHED |
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: Maroon 5 | Statement: [We Like Digging? (as Kara's Flowers), hasSuccessorBandName, Maroon 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorBandName Context triple: [We Like Digging? (as Kara's Flowers), hasSuccessorBandName, Maroon 5]
-
A.
laterBandName
chosen
Indicates that the second band name is a new or subsequent name adopted by the same band that previously used the first band name.
-
B.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
-
C.
hasFatherBand
Indicates that a musical group or band is related to another band that is considered its originating, parent, or predecessor band.
-
D.
hasBandmates
Indicates that two or more individuals are members of the same musical band or group at the same time.
-
E.
hasSuccessorClubName
Indicates that one club’s name is followed or replaced by another club’s name, typically due to succession or rebranding.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:14 p.m.