Triple
T34019167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jake Roche |
E872331
|
entity |
| Predicate | hasBandNameChange |
P60916
|
FINISHED |
| Object | Rixton later renamed Push Baby |
—
|
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: Rixton later renamed Push Baby | Statement: [Jake Roche, hasBandNameChange, Rixton later renamed Push Baby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBandNameChange Context triple: [Jake Roche, hasBandNameChange, Rixton later renamed Push Baby]
-
A.
hasOriginalBandNameOf
Indicates that one entity is the original band name used by another musical group or artist.
-
B.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
C.
underwentNameChangeTo
chosen
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
D.
hasNameBeforeChange
Indicates that an entity is associated with the name it had prior to some change or renaming event.
-
E.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 1:51 a.m.