Triple
T27158127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rump Shaker |
E682577
|
entity |
| Predicate | radioEdit |
P25064
|
FINISHED |
| Object | Rump Shaker (Radio Mix) |
—
|
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: Rump Shaker (Radio Mix) | Statement: [Rump Shaker, radioEdit, Rump Shaker (Radio Mix)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioEdit Context triple: [Rump Shaker, radioEdit, Rump Shaker (Radio Mix)]
-
A.
radioSingle
Indicates that an entity is a single (individual) radio track or release, as opposed to an album, compilation, or other multi-track format.
-
B.
radioEditTitle
Indicates that a title refers specifically to the radio edit version of a work, distinguishing it from other versions.
-
C.
hasRadioEdit
chosen
Indicates that an entity has an associated radio-friendly edited version of itself.
-
D.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
-
E.
radioEmission
Indicates that one entity emits or produces radio-frequency radiation detectable as radio waves.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62508724481909a30255975def6e3 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:17 a.m.